|
So you should know that VB6 is single thread. Each window, timer, event is processed sequentially.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
|
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.)
|
|
|
|
|
I just created a WinForm app in .net, put a button with the click event taking 5 seconds to complete. When I click the button the GUI is non-responsive so I guess .net is single-threaded too.
|
|
|
|
|
den2k88 wrote: VB.NET has the same tools of C#, is more verbose and lacks a couple of features
There are also things VB.net does that c# doesn't.
|
|
|
|
|
Quote: BASIC was seen as the go to language for kids in
VB.NET simply isn't so. You know, VB.NET coding is by far more similar to C# than to VB6 .
|
|
|
|
|
That's why I went for C# instead VB when I moved to .NET. I had many years as a C programmer.
|
|
|
|
|
glennPattonWork wrote: 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...
That's just ignorance I'm afraid. Before .net, VB6 was the only real solution for Enterprise apps, and there was nothing wrong with using it. Almost all enterprise solutions from houses that used an MS stack ran on VB6. The fact that "B" stands for "BASIC" and you think "BASIC is for kids" is simply your opinion, it isn't reality.
|
|
|
|
|
Quote: "BASIC is for kids" is simply your opinion, it isn't reality It is neverthless, in my opinion too. And possibly in the ones of the language authors. The hint is in the acronym.
|
|
|
|
|
You're as equally entitled to your wrong opinion as the OP is
|
|
|
|
|
So you are. As matter of fact, your wrong opinion is more wrong than ours.
|
|
|
|
|
My comments are not opinion though, I've been involved in many complex, high-performance enterprise applications built on VB6.
|
|
|
|
|
Quote: high-performance enterprise applications built on VB6 I agree that can be done (and top developers did).
My comment applies to the (original) language name ('beginners' is there).
Then one might discuss on the mass of mediocre developers attracted by VB6 , but that's just another topic.
|
|
|
|
|
CPallini wrote: Then one might discuss on the mass of mediocre developers attracted by VB6
Would love to talk about that but I'm busy in QA helping the mass of mediocre developers attracted by c#.
|
|
|
|
|
Well, C# is mainstream like VB6 was.
|
|
|
|
|
My point was that the users do not reflect the language.
|
|
|
|
|
That's the answer then. Users grow old and gray trying to see themselves in the mirror.
See me now!
|
|
|
|
|
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...
|
|
|
|
|
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...
|
|
|
|
|
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...
|
|
|
|
|
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.
|
|
|
|
|
VB6 was widely used though. I suppose it is still fairly used.
The typical recipe (I am ware of) was: VB6 for the bulk of the application code, aided by small C++ COM DLLs .
|
|
|
|
|
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.
|
|
|
|
|
VBA (what drives the macros in office) was VB6 embedded in Office, VB6 came first. VBA is Visual Basic for Applications.
|
|
|
|