When .NET came along MS replaced "classic" VB with VB.NET, which was syntactically just different enough from classic VB to make moving to it a big project.
Worse, VB.NET wasn't backwards-compatible with classic VB, so you couldn't just bring your old projects into the new environment; you had to rewrite them from the ground up in the new syntax.
Worse still, to encourage VB devs to move to VB.NET, Microsoft stopped selling licenses for classic VB. Not "warned developers they would stop selling licenses in five years" or the like, mind. They just stopped. If you wanted to buy a license for VB, it was VB.NET or nothing. Which, when you considered that VB.NET wouldn't run all your old code, was kind of terrifying.
All of which amounted to dropping a nuclear bomb on the VB community, as it pushed everyone into doing what someone (I think Joel Spolsky) once called "the dreaded market survey." In other words, if you're going to have to learn a whole new language in a hurry anyway, why not consider all the new languages available to you?
So while a few classic VB devs did move to VB.NET, most ended up landing elsewhere; some to C#, some to web application platforms like ColdFusion, some to open-source languages like Perl, etc. (I went to Perl, which led me to PHP, which led me to Python.) What had been one of the world's largest programming communities was scattered to the four winds overnight.
It would have been (maybe still would be) amazing to see what the community would pull off with VB6 if Microsoft would open source it.
VB6 IDE was so far ahead of it's time, even today (20+ years later) most languages don't have anything that comes close to what Microsoft had done there in the 90s.
It would probabaly the perfect language for UI development and data analysis (think VBNotebooks), possibly ML.
The lack of a reasonable porting tool and the fact that it didn't really have any advantages over C# in .net land, it made sense for most people to jump to C# instead of VB.net.
MS had to know this was going to happen. They left the door open for someone to actually create something to fill the VB niche, but all the focus on web technologies has meant that nothing really stepped up.
This isn't necessarily a bad thing because it's hard to make both small projects and big projects happy at the same time. But MS decided to focus on "enterprise" because the profit margins are usually bigger there. Thus, they mostly abandoned the original VB.
This sent a shock-wave through the industry because their code base couldn't go anywhere. It did give a boost to FOSS, because it's less likely that a heavily used FOSS product will be outright abandoned.
VB6 (runtime and language) was great for its time but it's an evolutionary dead end.
> Was it because of Microsoft forcing VB into "just another skin" over .NET, i.e., a variant of C# that doesn't have curly braces? That's how it looks on the surface, but it's compiled, not interpreted, has an actual type system, threads, a proper standard library.
There's also the need to gather the C++ Win32/MFC crowd and the VB6 crowd into a single tent.
Maybe that was only the case in the '70s and '80s. I'm sure that if I had Python as a kid, it would have been just as easy to experiment as it was with BASIC back then.
The early interpreted BASICs did make it difficult to write good code. All source editing was line editing, every line was numbered, there weren't any structured control flow statements, composite data structures were limited to arrays and strings...
But even as early as the second half of the 80's there were mainstream implementations of BASIC that addressed all of these. Microsoft QuickBASIC 4 added a full screen editor and then completely relaxed the need for line numbering. Line numbers were still supported, but so were symbolic labels. QB4 also had support for functions/subroutines, decent control flow statements, and structured data types. There was also reasonable support for extension libraries, and the like. As long as you didn't rely on any code patterns that required any kind of callback or inversion of control, you could do a very nice job writing well factored and maintainable code.
You have to see this in historical context. That Basic had an editor was a huge step forwards. That it wasn’t a full-screen editor was because full-screen editors didn’t exist yet (who wants to wait for their teletype to print 24 lines, and waste half a page of paper on it?)
https://en.wikipedia.org/wiki/BASIC#Origin:
"The first version BASIC language was released on 1 May 1964”
https://en.wikipedia.org/wiki/Text_editor#History:
"One of the earliest full-screen editors was O26, which was written for the operator console of the CDC 6000 series computers in 1967.”
The sad part is that, because BASIC was supposed to be the "easy" programming language, it was frequently used as the language in which students were taught how to program. Which meant its bad habits ended up getting impressed hard onto a lot of impressionable minds. I spent years fixing all the ways first learning to program in BASIC had bent my brain.
I’m super grateful for little things like that. All those older people that were welcoming to me on those forums have a special place in my heart, and I’ve been thinking about them fondly while I build a compiler—something I wouldn’t have been able to do without them answering all my questions when I got stuck.
Later I spent a lot of time writing IRC bots and the IRC communities were equally as friendly.
The real light bulb moment for me was a PHP tutorial from, I think, W3Schools. There was this moment where I realized I could build this thing and with a single click anyone in the world with a computer and internet connection could consume it. Everybody has a web browser! That was the moment I realized I wanted to to be a web developer and I never looked back.
However, today there are far better languages that are easier and are better introductions to programming for beginners. Of those, Python is my favorite.
On a personal note, I collect vintage computers. I have too many and stopped counting at 50. So I do use BASIC in that sense.
It's actually more difficult to teach Arduino in a day or two and hope any of it sticks if the person you're training in coming in with zero programming background. BASIC is still an easy language for complete newbie to pick up in a short amount of time. The ease of learning comes at a cost later on though. I've encouraged teachers to start with BASIC if their students had no prior background or if they themselves feel overwhelmed by the wider pastures of the Arduino. I underscore that the time spent learning C++ in an Arduino context is a better investment than time spent mastering BASIC. BASIC is easy to learn for the purposes of the robot, but C++ can control the robot and allow you to branch out into countless other languages. I liken programming languages to spoken languages and learning C++ is like learning Latin. It may be obtuse and difficult at first, but once it clicks, you can easily slide into any number of other languages with ease.
I'm now not really beating the BASIC drum anymore, instead I talk up Python now that Parallax has released a bot built atop the micro:bit. It's limited in the amount of memory on board and python eats embedded memory for lunch. It's time well spent learning Python. It allows students to grow into "what's next" far easier. Kids that learn Python on something like this robot can easily write the same kind of code on a computer to have it do all sorts of things. Kids in camps that I've run (and students in my classroom years ago) love learning about the countless python libraries they can use. I casually point out "mouse" and they making "random mouse movement" scripts as a gag. I always "fall for it" each time. ("Oh no! What?! My mouse... it's jumping all over the place!!!" - met with giggles, high fives, raucous laughter, etc)
So, yeah, I actually still teach BASIC on occasion, but I'm more and more turning teachers into Python lovers and C++ for the Arduino.
BASIC was designed with a simple, algebraic syntax to enable non-experts to learn how to write simple programs in an afternoon, and Python seems to follow in that mold.
In fact, the following BASIC program runs fine in Python 2.7:
a = 2
b = 3
print "Hello, world! Let's do some math:"
print "a * b =", a * b
I've used it to make a business dashboard for my indie software business, a schedule estimating app using "evidence based" Monte Carlo methods, and I was working on a cross platform Micro.Blog client (inspired a lot by Tweetbot).
I teach kids to program via an after school robotics club and Python is so much easier and more powerful than BASIC ever was.
Occasionally I get nostalgic and break out a BASIC and its fun for a bit but I quickly realize how clunky the language really is.
It gets the job done. Part of my reticence is ignorance. I might have a meaningful opinion if I were familiar with more than just println and single line if/else. I am glad I don't need to plan for line numbering in any other realm.
I echo the sentiment of proxybop; the ability to type things and see something happen is a powerful motivator in learning to code. As a lot of commenters point out, Python seems to have largely replaced BASIC as the "beginner" language to help teach folks. The REPL reinforces this, imo.
It has some issues, but it's still probably the best possible tool for making cross-platform desktop applications.
I really enjoy the expressive power and/or other features of Swift, Go, and a few other languages, but if I could write code in only one language it would be an object-oriented BASIC like Xojo.
If you need to program in a particular language at your place of work, or you want to learn a language to compete for a job then that's a different matter. ;-)
I still break out the QBasic once in a while. I have it in DosBox for when I get the itch. In AppleWin I toy with Applesoft Basic. I also play a bit with QB64 which is a modern QBasic clone.
Normally I write code in C# or Python though. C# is my main language and it's what puts food on my table.
XBASIC, QB64, and various BASICs specific to old computers I still use, like MBASIC on my Osborne 1.
(prog ()
10 (print "hello")
20 (go 10))20 ???
30 GOSUB 10
40 PROFIT!