VB & C++ Topic Ealier Got Me Thinking...
-
VisualBasic was very much used in the real world.
Thats the thing that worries me, I mean a language for Beginners used for big systems, not an issue...
-
Hi All, VB was (is?) seen as the quickest way to write Windows apps. I came to Windows from the embedded side, really reading data coming in via various ports and showing in Windows. VB6 was the quickest way as the company was run by a Micro-Sharft consultant. But there was Borland's C++ Builder and Delphi as well, BASIC was seen as the go to language for kids in my day I started with BBC Basic and C came with the Amiga... I was a little shocked to find BASIC being used in the wild...
glennPattonWork wrote:
I came to Windows from the embedded side, really reading data coming in via various ports and showing in Windows. VB6 was the quickest way as the company was run by a Micro-Sharft consultant.
Before .NET, there was only two choices for embedded software; eVC or eVB. Gotta love your Mono :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
The B does not stand for BASIC, but for "BEGINNERS". With C++ and Delphi there were enough alternatives. VB6 was Access on steroids. VB.NET is born from that. --edit Who in their right mind would risc the existence of their enterprise by allowing VB-code?
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Access on Steroids...Hmmmm
-
CPallini wrote:
Then one might discuss on the mass of mediocre developers attracted by
VB6Would love to talk about that but I'm busy in QA helping the mass of mediocre developers attracted by c#.
-
My point was that the users do not reflect the language.
-
Thats the thing that worries me, I mean a language for Beginners used for big systems, not an issue...
It's not for beginners though, it's evolved from the initial BASIC but simply retained the name. If you want to prejudice decades of work based simply on a name then that only speaks of you. BTW, guinea pigs aren't pigs. Sorry to break that to you...
-
glennPattonWork wrote:
I came to Windows from the embedded side, really reading data coming in via various ports and showing in Windows. VB6 was the quickest way as the company was run by a Micro-Sharft consultant.
Before .NET, there was only two choices for embedded software; eVC or eVB. Gotta love your Mono :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
The B does not stand for BASIC, but for "BEGINNERS". With C++ and Delphi there were enough alternatives. VB6 was Access on steroids. VB.NET is born from that. --edit Who in their right mind would risc the existence of their enterprise by allowing VB-code?
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Eddy Vluggen wrote:
The B does not stand for BASIC, but for "BEGINNERS"
I was referring to the "B" in "VB".
-
Eddy Vluggen wrote:
The B does not stand for BASIC, but for "BEGINNERS"
I was referring to the "B" in "VB".
So was I. The B in VB stands for BASIC, which is a "beginners allpurpose symbolic instruction code". The real humor was in MS selling a "professional" version of the product. I have worked for these kinds of professional beginners :thumbsup:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
So was I. The B in VB stands for BASIC, which is a "beginners allpurpose symbolic instruction code". The real humor was in MS selling a "professional" version of the product. I have worked for these kinds of professional beginners :thumbsup:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
That might be true if it was Visual BASIC, but it's not, it's Visual Basic. The Basic in VB is not an acronym, it is to reflect the roots of the language.
-
Only for big embedded products that didn't use a Micro-controller. C still rules the small world!
-
That might be true if it was Visual BASIC, but it's not, it's Visual Basic. The Basic in VB is not an acronym, it is to reflect the roots of the language.
It is just another BASIC-dialect. It doesn't just reflect the root, it reflects the targetted audience. VB is one of the few languages where people can be "productive" without much knowledge of the system they're working on. That in itself is reflected again in the quality of the products built with it.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
I didn't mean to start a fight, BASIC is Beginners All purpose Symbolic Instruction Code, I heard all the way BASIC isn't used in the real world...
I programmed in Amstrad CPC 6128 (#Griff #signature) in BASIC, and this basic has nothing to do with VB6. It was _really_ for beginners. I would not describe VB6 as good performing, but there was some point of time where it was one of the only choices available with a great compatibility with MSOffice tools. Actually, the success of it probably came from the Macro tools in Office, before it was a thing on its own, even when I am not 100% sure of what I am stating.
-
It is just another BASIC-dialect. It doesn't just reflect the root, it reflects the targetted audience. VB is one of the few languages where people can be "productive" without much knowledge of the system they're working on. That in itself is reflected again in the quality of the products built with it.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Eddy Vluggen wrote:
It doesn't just reflect the root, it reflects the targetted audience.
Not according to Microsoft.
-
Eddy Vluggen wrote:
It doesn't just reflect the root, it reflects the targetted audience.
Not according to Microsoft.
-
Yes, it is, now go troll somewhere else.
-
Yes, it is, now go troll somewhere else.
It has been well documented how Microsoft regretted naming it basic; the "professional" thingy was there to convince people that it was not "just" for beginners. It is not trolling, just history. And me disliking the concept does not make VB6 any less of a succes. --edit I would be extremely happy if one of my applications had 10% the success of VB6 :thumbsup:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
VB6 doesn't have proper builtin support for multithreading, but that doesn't mean you can't. You can: FreeVBCode code snippet: A Thread to Visual Basic: Multi-Threading In VB5 and VB6[^] But as they say: Just because you can do something, doesn't mean you should.
Wrong is evil and must be defeated. - Jeff Ello
If you've ever been touching a language with proper threading support built into the language from the very beginning design stage, you would completely reject the "multithreading support" that has been added to the C class of languages more like a cancerous growth; it is not at all any neatly integrated element of the language, as it ought to be. (You could say the same about e.g. exception handling.) Those who bitch at VB, should have something better to come up with than C. (My first choice would be CHILL, but that language never made its way out of the telephone switches where it was born - which is a pity, because it had really nice thread handling and synchronization mechanisms, as well as very good exception handling mechanisms.)
-
Thats the thing that worries me, I mean a language for Beginners used for big systems, not an issue...
Yeah, and an language developed for implementing a space invasion game, with a multiprocess concept designed for enabling the attacking space ships to come closer and closer as you were pondering what to do next, a user interface created for you to shoot down the alien attackers... Languages, operating systems and command processors sometimes have origins that shouldn't make you proud.
