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 521521
To read all comments associated with this story, please click here.
by Morgan on Mon 11th Jun 2012 00:55 UTC
Member since:

VB6 was one of several programming languages I studied in college, and I actually really enjoyed it. I remember writing a custom MP3/CD player for my best friend for his birthday; I believe I still have the source files archived somewhere.

Unfortunately I never was very good at anything more complex than that, and shifted to the networking and web design classes. What I did learn helped with PHP and JavaScript though.

Now I want to dust off those old files and eBooks, and start coding again! It's nice to know Microsoft will allow me to run those buggy, insecure apps in Windows 8. ;)

Reply Score: 5

RE: Memories...
by zima on Mon 11th Jun 2012 06:17 in reply to "Memories..."
zima Member since:

Unfortunately I never was very good at anything more complex than that


It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration.


(but more seriously: if you want to revisit it, you might also look into Gambas or, particularly, XNA ...yeah, in the latter, not exactly the same - but OTOH easy dev on Windows Phone, among other targets, and IIRC you want to get WP handset)

Reply Parent Score: 2

RE[2]: Memories...
by Morgan on Mon 11th Jun 2012 06:29 in reply to "RE: Memories..."
Morgan Member since:

Actually my lack of programming skill stems directly from my issues with math beyond basic calculus. While I understand logic and program flow, I don't have a good enough foundation for math-heavy languages. My skills lie in language arts, mechanical and electronics engineering, and to a limited degree, music theory.

And I do own a WP7 phone, I've had an HTC Arrive since November 2011 and for the most part I love it.

I would say the only thing bad about learning VB is that it is severely limited in scope, and also allows for lazy programming. It's comparable to Legos in practice, and it hits a plateau fairly quickly. In the same vein, building an R/C car out of Lego blocks is fine but you would never get a full sized vehicle that was functional with them.

Reply Parent Score: 2

RE: Memories...
by Tuishimi on Mon 11th Jun 2012 18:12 in reply to "Memories..."
Tuishimi 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