VB6: Best programming language ever
-
Demand doesn't make something "not bad" - see cigarettes, the first generation Fiat Panda, and Sharknado 2.
Perfect argument! Case closed! :laugh:
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
-
It wasn't a bad language. If it was a bad language, there wouldn't have been such a demand for it in the business community. It did exactly what it set out to do - make developing business applications quick.
-
Thank God! For a moment I thought you'd lost your mind. Everyone knows MicroFocus Cobol is second to none. Which is why it figures prominently on my resume. ;) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
On Error Resume Next
:mad::mad::mad:
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
A short while ago (like one or two months ago) there was a TOP article here on CP explaining that VB6 is a great language that should come back. It got quite some upvotes too. Just looked it up: Visual Basic 6.0: A giant more powerful than ever[^]. It even won VB article of the month. I'm not saying it's a bad article, the author clearly put time and effort in it, and I refrained from voting. I WAS very surprised by the article and the amount of people agreeing with it though. Thought you might have read it ;-)
-
A short while ago (like one or two months ago) there was a TOP article here on CP explaining that VB6 is a great language that should come back. It got quite some upvotes too. Just looked it up: Visual Basic 6.0: A giant more powerful than ever[^]. It even won VB article of the month. I'm not saying it's a bad article, the author clearly put time and effort in it, and I refrained from voting. I WAS very surprised by the article and the amount of people agreeing with it though. Thought you might have read it ;-)
What a bunch of crack smoking dullards!! I had to keep it kid sister safe...
A guide to posting questions on CodeProject
How to debug small programs
Dave Kreskowiak -
Then you can't like the
dynamic
keyword in C#. :)Wrong is evil and must be defeated. - Jeff Ello[^]
-
Then you can't like the
dynamic
keyword in C#. :)Wrong is evil and must be defeated. - Jeff Ello[^]
-
Pete O'Hanlon wrote:
make developing business applications quick.
That what you say - but in 1999 when we went to Microsoft they sold us VB6 to develop the new version of our ERP. It was catastrophic... It was a group - so-called - specialist in distributed network applications (they called it DNALab), and they almost ruined our reputation with that suggestion... So the fact that even Microsoft didn't know for what VB is good, but they tried it on everyone without mercy... X|
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
Kornfeld Eliyahu Peter wrote:
in 1999 when we went to Microsoft they sold us VB6 to develop the new version of our ERP
In 1999 Microsoft was selling VB6 for any business problem. It was their language of the day. :sigh:
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am. JimmyRopes -
Oh I don't like it. Too much typing. And I have seen some use it just because they can with no real purpose. Same treatment that
var
gets mostly.d@nish wrote:
Oh I don't like it. Too much No typing.
FTFY :-D
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am. JimmyRopes -
Oh I don't like it. Too much typing. And I have seen some use it just because they can with no real purpose. Same treatment that
var
gets mostly.Whenever I see
var
I have trouble dissociating it from the dreadedvariant
in the subject language, it still makes me shudder. Some silly bugger used a GoTo in a stored proc the other day, the reaction was not pretty.Never underestimate the power of human stupidity RAH
-
Whenever I see
var
I have trouble dissociating it from the dreadedvariant
in the subject language, it still makes me shudder. Some silly bugger used a GoTo in a stored proc the other day, the reaction was not pretty.Never underestimate the power of human stupidity RAH
-
It wasn't a bad language. If it was a bad language, there wouldn't have been such a demand for it in the business community. It did exactly what it set out to do - make developing business applications quick.
-
We still have many VB6 code around here (mostly batch and client legacy apps). The main reason behind is that the .NET framework is not installed on standard end user PC images.:mad:
The signature is in building process.. Please wait...
-
What a bunch of crack smoking dullards!! I had to keep it kid sister safe...
A guide to posting questions on CodeProject
How to debug small programs
Dave KreskowiakI agree with you whole heartidly though :laugh:
-
I realise I may get flamed for this, and I am mentally prepared for it, but VB6 was not as bad as people make it out to be. Sure it was not the best language for much of anything, but it is not as bad as people make it out to be. .NET was far worse, and I would even go as far as to say that C# is more shoddy than VB6 ever was or ever will be. Now before the flaming starts hear me out. I personally would class VB6 as an intermediary language, sure there was a lot more managed libraries than C++ will ever have, but the amount of managed code in VB6 pales in comparison to the amount of managed code in .NET or C#. As someone who has dabbled briefly into cryptography, managed code is the single largest bane of any language you can name. Unmanaged code also prods the coder to pay a hell of a lot more attention to what they are doing, to make sure they get things right, because getting anything wrong can lead to catastrophic failure, particularly in languages that have even less managed code libraries than VB6. So is VB6 the best language ever? No, but there are certainly a significant amount of more "modern" languages around that are significantly worse. Sure you could write some unsafe code in VB6, but if you are any good at it, you can write "unsafe code" that does the job it was written for, does it correctly, and is faster than the "managed code". In short, before anyone starts ranting about how bad a language is, learn the compiler properly, learn the loop holes, the does and the don't. You'll be happier, more productive code monkeys. When speed and accuracy is of prime importance to your application, unmanaged code is king. Quit with the hand holding that are managed libraries and learn to code properly.
-
Pete O'Hanlon wrote:
make developing business applications quick.
That what you say - but in 1999 when we went to Microsoft they sold us VB6 to develop the new version of our ERP. It was catastrophic... It was a group - so-called - specialist in distributed network applications (they called it DNALab), and they almost ruined our reputation with that suggestion... So the fact that even Microsoft didn't know for what VB is good, but they tried it on everyone without mercy... X|
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
So the problem was the people and not the language. MS fell victim to the same mentality as many large consultancies and tried body shopping where they'd drop a star programmer in to win the bid and, as soon as they had got the work, they'd drag that poor sap off to repeat the same process in other companies. It's known as bait and switch. You cannot blame the language for poor management practice. I've seen many fine programs written in VB6, in just the same was as I've seen many poor ones.