3 ms·
> You could always tell a VB app. Controls don't line up, windows either prevent resizing or do so badly, lots of redraw flicker, varying visual styles, and cra
by cm2187 5y ago
> You could always tell a VB app. Controls don't line up, windows either prevent resizing or do so badly, lots of redraw flicker, varying visual styles, and crashes on seemingly benign user input.
You are describing 1998 VB as much as 2022 html+javascript
- mschuster91 5y agoWith the obvious joke (or sad fact) that VB6 apps used to run on, like, 64 MB RAM systems (or less, if you were targetting Windows CE and had that extended tooling in Visual Studio for it) - and today for your average Electron or whatever browser based "app" you need 4GB+ of RAM.
- StillBored 5y ago64 MB RAM, not unusual for a high end desktop/dev machine in the late 1990's, but... VB6 (the last one) was 1998, same year as win98, which listed a 486+16M of ram as its system requirements. Which was a big step up from a W95 386 with 4M of ram. So one probably didn't want to run VB itself on those smaller machines, but the resulting apps definitely did, and those low end desktops were exactly what a lot of vb apps were running on.
- victorvosk 5y agoNot sure how much you are joking, but all the "apps were better in the 90s" blog posts overlook the absurd flexibility web apps have gained over the years. VB and its ilk were used to write apps that were used in a very specific way. Many times companies wrote apps not just their business use cases, but literally with the expectation of the hardware their users had in the office, the network they were on and who would be maintaining the machines. Ultra rigid user experiences, but still somehow were bug prone. Today its like, oh yeah, a user had an issue, they were searching our million record database on their smart toaster, one of the table columns weren't aligned correctly and it was slow to load.