Linked by Thom Holwerda on Mon 11th Jun 2012 00:38 UTC, submitted by judgen
Windows "Microsoft recently extended 'It Just Works' compatibility for Visual Basic 6 applications through the full lifetime of Windows 8. Visual Basic 6 first shipped in 1998, so its apps will have at least 24 years of supported lifetime. Contrast that with the Microsoft .NET Framework 1.0 (2002), which is incompatible with Windows 7 (2009)."
Thread beginning with comment 521697
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:


"This has nothing to do with the VB frontends, but everything with the backend."

Well, ActiveX, VBD's, DCOM, etc were an awful mess. They were far more painful to deploy than web applications. However your point is completely valid with respect to Local vs Web apps in general.

"Web applications suffer from the same issues, with the added complexity that part of the UI is also running server side."

Yep, "fat applications" often deliver a superior interface and consume fewer resources at the same time.

"As for web interfaces being pleasant. I curse every time I need to maintain a mountain of CSS/HTML/JavaScript garbage that could be easily done in a RAD tool."

Well, in theory a good RAD tool could encapsulate the CSS/HTML/Javascript bits on the web in the same way it encapsulates the win32s on the desktop, but in practice we have many kludges to compensate for web postbacks and needing to write interfaces in both client side and server side code.

Reply Parent Score: 2