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 521746
To read all comments associated with this story, please click here.
RE[5]: Memories...
by Laurence on Tue 12th Jun 2012 18:32 UTC in reply to "RE[4]: Memories..."
Member since:

VB did not offer full win32 api support. It did not handle pointers, which limited the api's it could call. ( Ironically VB5 had a trick which did make it possible, but MS closed that loop hole in VB6).

In the instances where pointers were required, there was usually a wrapper API.

VB didn't have to compile to P Code. Their was an option to compile to native code, which did perform better.

"Native code" wasn't technically native though. It was still managed byte code of some description and thus still suffered from major performance penalties.

It also still had OCX dependencies, which sucked hard given that ActiveX is one of the worst things to come out of Redmond since Bob and Me.

Reply Parent Score: 2