|
Ian Shlasko wrote: It was never meant for ... commercial applications
LOL says who? I've written many a commercial app and website using it, what else were we supposed to use?
It's like anything, the second it is superseded all of a sudden people talk like it's rubbish and always was. When .net is superseded people will be slagging it off saying how garbage it was, how assembly binding via configuration and convention was a stupid idea and so on.
|
|
|
|
|
I agree with you 100%! I'm not sure how the syntax of a join can be blamed on VB anyway???
"Go forth into the source" - Neal Morse
|
|
|
|
|
F-ES Sitecore wrote: It's like anything, the second it is superseded all of a sudden people talk like it's rubbish and always was. When .net is superseded people will be slagging it off saying how garbage it was, how assembly binding via configuration and convention was a stupid idea and so on.
Exactly. VB was a perfectly good tool that enabled businesses to get mission critical applications into production sooner than later. I read that a large chunk of VB6 applications are still in production today. [in 1981 I was told that COBOL was dead and it wasn't worth learning. Scary how much COBOL is still in production today, doing what it needs to do.]
Were a lot of crap applications written in VB? Absolutely! But a lot of crap applications are now being written now in C#, Java, etc. And yes, the next generation will whine about how crappy C#, Java, etc. were.
Blaming the software for what people do with it is like blaming the hammer when you miss a nail and put a hole in the dry wall.
|
|
|
|
|
Quote: It was never meant for high-end computing or commercial applications, And yet it is used for both, I know of at least one application where when it was found the reaction was "Oh No, change it!" Followed by "Well it has worked reliably for the X years, trust us you don't want to mess with this code as it is too wide spread to make a fix all update". It is used in flight control systems of a very well known heavy lift helicopter.
|
|
|
|
|
glennPattonWorking wrote: It is used in flight control systems of a very well known heavy lift helicopter.
|
|
|
|
|
When I was include on the Email chain it was truely a moment. what better (or worse) it was using VB5!!
|
|
|
|
|
Ian Shlasko wrote: It was never meant for high-end computing or commercial applications
Are you sure? Microsoft had - 16-17 years ago - DNA Labs all over the word, where Microsoft gave the help to port enterprise-scale applications to VB6...
My boss felt for it and I spend there half a year and cursed for an other two, before we moved back to c++...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Microsoft gave the help to port enterprise-scale applications to VB6...
Kornfeld Eliyahu Peter wrote: My boss felt for it
And there's your problem. As professional geeks, it's OUR job to look at a tool/language/framework and see how it should be used.
This is how it's supposed to happen:
Company X: "This is awesome and can do everything!"
Your Boss: "This is awesome and can do everything, and I'm not saying that because they gave me a bribe completely non-conditional gift! Let's use this for everything!"
You: "This is a horrible idea, and if we actually use this, we'll probably all end up getting fired/bankrupted"
Your Boss: "Oh, ok then. I gotta go. I have a meeting with Company Y."
|
|
|
|
|
Almost perfect dialog...except the last line...
(and 18 years ago a was pretty fresh)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Oh, the last line was just my way of saying "GOTO start"
|
|
|
|
|
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Marc Clifton wrote: e.TerminalType *= f.TerminalType
I've been forced to use that format when writing for older Oracle systems.
So, it may not be the language that is/was the issue, it may be the data source.
The implication being.. such a join may be seen in other languages like C, C#, etc.
|
|
|
|
|
I recently encountered ( +) in an Oracle query.
It's the same thing, except this query was written a week earlier...
I had never seen that syntax by the way, not in Oracle or SQL Server
|
|
|
|
|
The *= syntax is Sybase, SQL Server until 2000 and Access
|
|
|
|
|
... aaand back to therapy...
|
|
|
|
|
I never did that myself, even though it seemed to be all the rage.
But it's normal for common coding conventions to be superseded by others (most of which are not genuinely better; just different), and for the superseded conventions to be reviled.
It's a "The Winner Writes the History Books" thing.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Quote: e.TerminalType *= f.TerminalType
Isn't that just e.TerminalType = e.TerminalType * f.TerminalType ?
|
|
|
|
|
In code, yes. In SQL that's an old-style JOIN syntax.
http://sqlmag.com/t-sql/old-join-syntax-vs-new
|
|
|
|
|
We have a story (Gah! I hate Agile terminology.) to remove all those from our codebase. There are enough to make that a 2 sprint story.
|
|
|
|
|
Hi All,
Still in new job mode, after some early success with the Hardware issues I have now been given the issue of the software bug that is halting work on a new product. I can after a mornings worth of installs confirm the software works on the demo board. Now to run it on the board and see what is missing and why it does not work It's gonna be a three job at least, possibly a job too.
|
|
|
|
|
As long as it doesn't turn in to a hard liqueur job.
|
|
|
|
|
Will you change your name to 'PUB' before or after getting the ?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
...Anybody[^]???
SFW
Anything that is unrelated to elephants is irrelephant Anonymous
- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944
- I'd just like a chance to prove that money can't make me happy. Me, all the time
|
|
|
|
|
01110011 01101000 01110101 01110100 00100000 01110101 01110000 00100000 01100001 01101110 01100100 00100000 01110100 01100001 01101011 01100101 00100000 01101101 01111001 00100000 01101101 01101111 01101110 01100101 01111001
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|