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)."
Permalink for comment 521561
To read all comments associated with this story, please click here.
RE[3]: Memories...
by Laurence on Mon 11th Jun 2012 10:12 UTC in reply to "RE[2]: Memories..."
Laurence
Member since:
2007-03-26

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.


People are often quick to dismiss VB6 but it actually had a lot of hidden power. I remember being taught VB6 at college and I'd written a 2D racing game in DirectX7. VB also offered the full range of Win32 API's that C++ had (all reasonably well documented too). In fact you could call pretty much any DLL so long as you knew the function name, inputs and returns.

The biggest weakness with VB6 wasn't the language itself but actually the compiler. Visual Basic was massively crippled by Microsoft's insistence to compile to P-Code with ActiveX dependencies. While I understand the managed code like VB requires some level of runtime interpretation, the objects created from VB's compiler were just terrible. But I guess back then visualised runtime environments were very much still an emerging technology.

Reply Parent Score: 5