|
Agreed. VB wasn't perfect for ~everything~ but it was Rapid Application Development at its best. The massive simplification of otherwise gangly code with all of it's built in functions is what made it so friggin' popular. VB6 was the most used programming language on the planet when MS pulled the plug and VB.NET was in the top 3 when MS just started drifting away from supporting it. Amazing how you can have a product so popular and just chuck it...twice. Dumping the language like that is what makes me not trust investing time learning and collecting code for anything proprietary to MS. No customer loyalty.
|
|
|
|
|
It's more down to the editors and compilers supporting the language.
I could undoubtedly compile my own VB files and run them on .NET 6 (I'm assuming the resulting MSIL will run fine, but it isn't guaranteed as Microsoft seems to have dropped support).
However, Visual Studio doesn't support VB projects anymore, so I'd have to do it all manually, which is a pain, and not viable for a professional project.
And, as said, it's not VB.NET generating the MSIL, but the compiler, and when Microsoft drops support for that, it could be possible that VB.NET becomes incompatible with newer versions of the framework.
|
|
|
|
|
I have VS 2022 and it supports VB.
|
|
|
|
|
Visual Studio does support VB.Net - but it has never supported VB (Visual Basic 6, Visual Basic 5, etc.).
|
|
|
|
|
was it ever alive ? dat it da question.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Judging from the amount of VB code that's still around it was very much alive.
|
|
|
|
|
It pioneered component (vs object) oriented development; a pattern which is useful today.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Quote: It pioneered component (vs object) oriented development; a pattern which is useful today.
I'm pretty certain that it did not; unless my memory is failing me (and at this age that is very possible), components were part of the Windows tech stack since '92 (COM and/or OLE). VB, like other Windows programming language tools, could use them.
IOW, they were installed with Windows, not with VB. VB was just the most popular way of writing Windows programs for well over a decade.
|
|
|
|
|
Component-based "architecture" was about reuse; not "COM" or "OLE" in particular.
VB was popular because of drag and drop (components).
The "RecordSet" (a component) was fundamental to sane client-server development.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
I used DragNDrop in a Windows Forms project using VB.Net (which will also work using C#). It's definitely a nice feature.
|
|
|
|
|
Quite a few folks don't know that MarshalByReferrence has been around for decades all the wat back to the Win 9X days... And everyone has forgotten the real roots in COM!
|
|
|
|
|
VB is among the walking dead of programming languages. Ruby is its sidekick. There's undoubtedly more.
|
|
|
|
|
Sometimes I feel like I am beating a dead Horse. 
First, Haters are going to hate.
Second, programmers, for the most part, like and defend the language they know best, and disparage almost every other.
Third, VB isn't "cool" anymore.
Fourth, the main problem with VB is the word "Basic" in the name. Particularly the "B" which stands for "Beginners".
For Sander. No, it is not dead. See steveb's post above about MSIL.
For Griff I sincerely, greatly appreciate your knowledge, wisdom, and the fact you help a whole lot of people in this site, myself included.
However, if you don't like "OnError Resume Next", or "OnError GoTo" (which is also found in C#), then DON'T USE THEM.
Saying that VB should be dropped because of those statements, is like saying all tigers, extremely beautiful animals, should be killed because they might bite your head off when you try to pet them. Or saying that most women should be killed because they are a PITA.
IMO this is not only foolish, but ridiculous.
Finally, I am pretty sure that quite a lot of businesses are still using VB6 and VB.net to run their business, if not the majority. And I apologize for not being one of the "cool kids" and being subject to my second observation above myself.
Sometimes one man's trash is just trash, but not in the case of VB.
|
|
|
|
|
I think Sanders point was that the tooling for VB.Net is lagging behind the more main stream c#. And yeah lots of people like to kick the old VB dog but there are also a lot of us that cut our teeth on it.
I got a hell of a shock a few years ago when I tried to show a newbie (school kid) how vb worked, I could it even connect to the database it had changed so much.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
Yeah, I agree with you on all points.
Slow Eddie wrote: For Sander. No, it is not dead. See steveb's post above about MSIL.
See my reply though.
The tooling seems to lag behind and Microsoft seems to not update VB anymore, making the gap with C# even bigger in the future.
Sure it's not "dead" because many people and companies still use it, but it doesn't seem like a good alternative for new development anymore.
In the end, VB.NET can do everything C# can (or it could a few years ago) and you can write good and bad code in both languages, but how long will this be true?
So by "dead" I mean Microsoft isn't actively developing it anymore, making it a no-go for new development.
|
|
|
|
|
I agree that that is no good reason to hate a language.
I remember having to do some changes in a VB6 project many many years ago, there was a dynamic form, which means that when the user chooses a value from a combobox than some controls could be created at runtim (depending on the choice)
I don't remember if it gave a compile error or a runtime error, what I do remember is that it did not worked as we expected, so we called for microsoft support which the company paid for.
Their answer was that this is by design, VB did not allow creating controls in the closeup event of a combobox...
I did not liked the language before this, but at that time I did became a real hater.
There are so many examples of stuff in this language that was unbelievable, there are so many reasons not to like it.
But agreed, the reasons you mention are not reasons to hate it.
|
|
|
|
|
I believe the largest "railroad" in North America runs COBOL and IMS for it's backend and VB for it's front end (because I worked on that project and can't see the effort required to change).
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Eddy, well said!
I recall creating Windows applications prior to VB3 ... GAWD! That was ugly. The rise of VB brought about far quicker development times as we didn't have to re-create the wheel by inventing new atoms each time.
I also recall other vendors playing catch-up, trying to emulate VB's drag-n-drop. Other vendors saw some success, but VB set the stage for modern development.
After MS terminated VB6, I stuck with it for several years, then tried VB.NET for a year. I saw the handwriting on the wall, jumped to C#, and that's been my primary language since then. VB.NET is not dead, but support for it is less and less each year -- at this point I'd not bother with it. But I also have a consultant's POV, so anything that doesn't increase my marketability loses my interest.
|
|
|
|
|
|
And RemObjects "Mercury": VB for all platforms ... for a bunch of $$$ but it exists!
I cannot remember: What did I before google?
|
|
|
|
|
Darwin's Theory: Humans are a product of evolution and what is produced by them falls under these rules, that means programming languages too.
|
|
|
|
|
was it ever really alive then ?
|
|
|
|
|
We started using C# many years ago (10 years or so). Although we've had to continually adjust/tweak our dependencies, mainly due to interactions with SQL Server and backup functions, it has done the job for us. I learned VB in college, but we are strictly C# now. We moved away from WinForms due to some inherent functionality restrictions that were cramping our style.
|
|
|
|
|
What were the functionality issues that were the problem? I use Windows Forms!
|
|
|
|
|
VB.NET and VB, probably are dead-ish as everyone above has discussed. VBA, which is VB for Office apps, is most definitely not.
Bond
Keep all things as simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
