Live data from Hacker News

Something Pretty Right: The History and Legacy of Visual Basic

retool.com

141–150 of 269 posts

Re: Something Pretty Right: The History and Legacy of Visual Basic

#141

Couple of thoughts: 1. Microsoft did a good thing at that time with Visual Basic. Building visual interfaces with RAD tools is the most efficient way, as defining visual elements with code is harder. VB was great at its time, Borland Delphi and C++ Builder were good, QT Builder was good, Windows Forms was good. Of course, why use good models when you can inflict pain and let people define UIs by using plain code? WPF…

I’ve started looking into MAUI over the last week and it honestly seems like a big improvement over Forms, in various ways.

Though it’s probably risky to use in production.

Re: Something Pretty Right: The History and Legacy of Visual Basic

#142

The WYSIWYG GUI builder that VB provided, I have never encountered afterwards again in quite that manner. Now, in VBs heyday the field of UX design we now have as a profession adjacent to software development was in its infancy and was usually an implicit part of the developers job. What was lost with the demise of the RAD tools was a potentially shared medium of expression. Today designers build Potemkin villages in…

I think the WYSIWYG WPF and Silverlight tools were pretty close to VB6 level of usability. The tools are great for building a quick UI, but I think they fall short for more complex applications. This is why designers have their own preferences when it comes to designing the UX, to give them the flexibility to create the UI as they see fit. When different teams are working on a shared goal, there can always an element…

I would argue that "more complex applications", when it comes to UI, are an anti-pattern. Use standard widgets, and don't be creative.

Of course "standard widgets" don't really exist anymore because of where UI design has gone, but they did provide a consistency that users could rely on. That is gone now. Buttons don't even look like buttons anymore.

Re: Something Pretty Right: The History and Legacy of Visual Basic

#143
post #28

Hilarious quote (notwithstanding the fact that bus drivers usually have to work shifts, also on weekends): > Almost all Visual Basic 6 programmers were content with what Visual Basic 6 did. They were happy to be bus drivers: to leave the office at 5 p.m. (or 4:30 p.m. on a really nice day) instead of working until midnight; to play with their families on weekends instead of trudging back to the office. They didn't la…

VB to VB.NET was more to do with .NET arriving with the .NET Framework, and one of the reasons for the .NET Framework was all about keeping up with the (at the time) amazing framework/core library that Java had. It was also about web front ends which of course VB6 could not do. In the old days people used to custom-build massive CRUD desktop database applications for their company to use internally and I built some o…

Standard was like $79

Pro $495

Re: Something Pretty Right: The History and Legacy of Visual Basic

#144
post #102
post #62

Earlier quoted context omitted.

Excel is another amazing piece of software, that is almost universally looked down upon by programmers. Why make complex calculations in a GUI if you can just write a Python script with numpy and pandas!? And yet, so much of the world runs on excel spreadsheets being sent back and forth. Why? Because 1) it has a low skill floor and very high ceiling, 2) everyone uses the same tool (or at least it's backward and forwa…

Excel is another amazing piece of software, that is almost universally looked down upon by programmers. I read somewhere that there are 10 x more Excel "programmers" in the world than programmers for all other languages put together.

I would not be surprised. I have said before that Excel is the most widely used programming environment in history and will continue to be so for the foreseeable future, and it is all precisely because it provides users an on-ramp to programming in a domain where it is sorely needed.

Re: Something Pretty Right: The History and Legacy of Visual Basic

#145
post #50

Earlier quoted context omitted.

Mind if I ask what you allow on your systems, today? Or the last time you worked in IT? (Not clear if you moved away from it or not)

Moved away by own choice. Never looked back.

Ok, fine.

But again, what did you "allow" on the systems you managed back in the day?

Re: Something Pretty Right: The History and Legacy of Visual Basic

#146
post #28

Hilarious quote (notwithstanding the fact that bus drivers usually have to work shifts, also on weekends): > Almost all Visual Basic 6 programmers were content with what Visual Basic 6 did. They were happy to be bus drivers: to leave the office at 5 p.m. (or 4:30 p.m. on a really nice day) instead of working until midnight; to play with their families on weekends instead of trudging back to the office. They didn't la…

Well - basically, if you wanted to become a fighter pilot and had VB1-6 experience and wanted the "RAD" forms tools, but also wanted true OOP, there was always... Delphi You could do pretty much anything with Delphi that you could do with C/C++ on Windows.

True, but that's also true of .NET

Re: Something Pretty Right: The History and Legacy of Visual Basic

#147
post #28

Hilarious quote (notwithstanding the fact that bus drivers usually have to work shifts, also on weekends): > Almost all Visual Basic 6 programmers were content with what Visual Basic 6 did. They were happy to be bus drivers: to leave the office at 5 p.m. (or 4:30 p.m. on a really nice day) instead of working until midnight; to play with their families on weekends instead of trudging back to the office. They didn't la…

Fair but I wanted to be a fighter pilot because the money was better than driving a bus. So I learned c#. The company I worked for, a software dev house, said that they were VB only be they wouldn’t bring in c#. They died within 6 months of me and everyone else leaving.

C# and .Net was a gold rush. VB was only valuable where the primary business function was not software delivery.

Re: Something Pretty Right: The History and Legacy of Visual Basic

#148
post #141

Couple of thoughts: 1. Microsoft did a good thing at that time with Visual Basic. Building visual interfaces with RAD tools is the most efficient way, as defining visual elements with code is harder. VB was great at its time, Borland Delphi and C++ Builder were good, QT Builder was good, Windows Forms was good. Of course, why use good models when you can inflict pain and let people define UIs by using plain code? WPF…

I’ve started looking into MAUI over the last week and it honestly seems like a big improvement over Forms, in various ways. Though it’s probably risky to use in production.

Yes it is nice, but I hope that once people and companies will make an investment in it, they won't deprecate it in favour of a new thing.

Re: Something Pretty Right: The History and Legacy of Visual Basic

#149
post #121

The WYSIWYG GUI builder that VB provided, I have never encountered afterwards again in quite that manner. Now, in VBs heyday the field of UX design we now have as a profession adjacent to software development was in its infancy and was usually an implicit part of the developers job. What was lost with the demise of the RAD tools was a potentially shared medium of expression. Today designers build Potemkin villages in…

The WYSIWYG GUI builder that VB provided, I have never encountered afterwards again in quite that manner. At the time I think delphi did that concept in a better way, and I definitely switched from VB to Delphi as soon as I learned about it. Delphi still exists to this day. There are also many low code platforms which have a VB-like UI builder, like mendix, or outsystems or microsoft’s power platform, but they tend t…

I remember in Access(for like $100 one time) and how you could use a wizard to build like a contact manager with all the tables and forms. I always thought that was really cool. Now I guess you can spend like $30/user per month or something like that.

Re: Something Pretty Right: The History and Legacy of Visual Basic

#150

Earlier quoted context omitted.

Very droll, but incorrect. Also, I believe the word you're looking for is purism . I'll certainly go along with that. Also also, out of curiosity, where did you dredge up the "he"?

For what it's worth, the male form is generally used when gender is unknown. I suspect those linguistic defaults will start changing soon.

It's being replaced by they. Which I'm fine with btw.
Post reply on HN