Live data from Hacker News

Ask HN: Why did Visual Basic die?

news.ycombinator.com

221–230 of 535 posts

Re: Ask HN: Why did Visual Basic die?

#221
VB was a godsend for me. Despite being a very capable DOS and embedded/RTOS developer, the learning curve for the ugly tools and API's for Win3.1 development was more than I wanted to handle.

It was magical how easy it was to build little tools and line-of-business apps in VB. And after eventually learning MSVC and MFC/ATL, I was even more impressed with how easy VB was compared to that.

But .Net killed VB because C# was enough for both noobs and for real programmers.

Re: Ask HN: Why did Visual Basic die?

#222
First of all, desktop software just isn't as popular as it used to be. Everyone wants to develop a webapp or a packaged app.

Second, Microsoft consolidated all of their languages into .NET right around the time you're describing, and they all get translated into the same middle language before being compiled. Maybe except C++? Not sure. Either way there's really no reason to choose VB when you can have C# and they all get converted to the same thing.

Lastly, Basic was always seen a "hobby" language, a reputation which was carried over to Visual Basic. So once again, serious programmers will look at the Visual Studio suite and go with C# or C++.

Re: Ask HN: Why did Visual Basic die?

#223

The productivity wasn't really that good. Rose tinted glasses. All the VB apps I've seen (and still get paid to maintain/rewrite to this day in the finance world) are an order of magnitude simpler than even a simple modern website. They often only have a few users, no devops automation, no deployment automation, terrible logging, terrible instrumentation, no tests, unacceptable access control, tons of failure edge ca…

You should think about what the alternative was at the time: Mostly C/C++

VB6 you would have connected to the db by the end of the day. C/C++ you're still trying to handle WM_ERASEBKGND

Re: Ask HN: Why did Visual Basic die?

#225
post #40

VB (and BASIC in general) has a legacy of being a procedural language. In the late 90’s and early 2000’s, there was a massive push to leverage object oriented programming and design. The births of Java in the 90’s and then C# in the 2000’s were clear catalysts to abandon procedural programming. Of course in .NET VB has nearly all of the OO capabilities that C# has, but I think most developers just decided to go “all-…

Honestly, I was never a fan of Basic but I still don't understand why there isn't a GUI app builder as productive as the VB6-era tools were for any language.

You can still build WinForms apps using C# or VB.NET, and they will even run on the latest .NET (v7). I built a little WinForms GUI utility that takes a CSV file with mappings from old URLs to new URLs, and generates a rewrite map for use in IIS, when rebuilding a website. I just place all my logic in a separate project so I could replace the UI in the future with a web interface or WPF, etc.

Re: Ask HN: Why did Visual Basic die?

#227
I do wonder if there’s an alternate universe where MS did a better job of modernising VB (VB.NET hardly counts), and where Borland was less doggedly intent on murdering their golden Delphi goose, and where frontend development is now quite easy.

Re: Ask HN: Why did Visual Basic die?

#228
It's similar to Microsoft Access. Not for everyone, but still did some things few other tools do out of the box.

VB was a form of relatively low code, relatively speaking to other ways of building applications.

There was a swing from the desktop to the web, but it wouldn't be unrealistic to say building web apps that render the same html/js/css became at least a few orders of magnitude more complex during that time too.

There remain personalities, belief systems and practices that believe things should be difficult and not easy to become a beginner in for it to have value for a few instead of the many.

Re: Ask HN: Why did Visual Basic die?

#229

Not just VB, but also things like Borland Delphi. 25 years ago, you could visually compose a UI using standardized components, including advanced concepts like a layout manager. You could do data-binding visually by navigating a linked database. You can write logic/events just by double-clicking a button and the event is created. Here you'd write your code which would typically be pretty easy because all contextual o…

Having used both early in my career, Delphi absolutely shat on VB. But I'd be really interested to see the code I wrote in the 90s and see how it stands up in terms of reliability, maintainability, testability etc.

The closest thing I've found in the modern age is https://anvil.works - basically works like Delphi/VB, but web based, and in Python. For both frontend and backend.

Re: Ask HN: Why did Visual Basic die?

#230

The productivity wasn't really that good. Rose tinted glasses. All the VB apps I've seen (and still get paid to maintain/rewrite to this day in the finance world) are an order of magnitude simpler than even a simple modern website. They often only have a few users, no devops automation, no deployment automation, terrible logging, terrible instrumentation, no tests, unacceptable access control, tons of failure edge ca…

Maybe not all apps need the complexity but portability.
Post reply on HN