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 521532
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: kill -9 now...
by Nelson on Mon 11th Jun 2012 05:37 UTC in reply to "kill -9 now..."
Nelson
Member since:
2005-11-29

To be fair though, from .NET 1.0 (and 1.1) to 2.0 was an world of a difference. Generics came and changed the game.

The 2.0 CLR still powers the .NET4 runtime today. So, that's a great track record of support.

Besides, .NET SxS deployment in Windows makes backwards compat a breeze..

On the topic of VB6: Its bemoaned now, but it is the IE of programming languages. When IE6 came out, it was this awesome, standards compliant, FAST thing. It just had the unfortunate luck of living too long.

The same applies to VB6. VB was the shit for its time, and it beat the pants off of C++ and the COM black magic that Microsoft though was useable.

Shops were happy to eat the perf cost of VB6 if it meant not having to do another AddRef/Release or QueryInterface, or compile an IDL file.

It did, for all intents and purposes, "Just work".

Reply Parent Score: 5

RE[2]: kill -9 now...
by sreque on Mon 11th Jun 2012 14:48 in reply to "RE: kill -9 now..."
sreque Member since:
2010-09-10

Actually, .NET 4.0 use a new version of the CLR.

Reply Parent Score: 2