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 521582
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Memories...
by Tuishimi on Mon 11th Jun 2012 18:12 UTC in reply to "Memories..."
Member since:

When I worked for [an unamed company] we wrote some serious applications in VB 5, then 6. It was nice because VB took a way a lot of the time/pain involved in creating the UI.

I say serious... by that I mean applications that were used to manage physical assets, stockroom inventory and ordering, mortgage life cycles, stuff like that.

I worked for a bank at one point and half their code was written in VAX BASIC, the rest in C and Assembly Language. [EDIT] In that particular division of the bank... LCs and BAs.

I enjoyed extended versions of BASIC. I enjoy the Euphoria language for implementing web apps as well. (Not that I use that for WORK... mostly Java these days).

DEC used a language called BLISS for much of their system development. It had a lot in common with Pascal and VAX BASIC. I used that for most of my work (BLISS) when I worked at DEC in VMS land. That and Assembly. And Ada.

But VB was sweet... if you could visualize the flow of the app properly you could whip up a UI in no time. Sure it was slow and somewhat limited in some aspects, but I wrote libraries for more complex data structures and simply used them when I needed to do some interesting data mapping and management.

Edited 2012-06-11 18:13 UTC

Reply Parent Score: 4