| > And Active Desktop... Hailstorm... SPOT | > watches... Windows LIVE... .Net ...VB | | .NET is still alive
I included that because it will be left in the lurch if Metro apps take over and MS closes down the OS to 3rd-parties. .Net was designed for corporate intranet applets and web services that never materialized. It was never well suited to Windows software -- just a slow and superfluous Java-esque wrapper with gigantic dependencies. Now .Net is one of the tools that can be used to write Metro apps. Another is javascript. That makes .Net look like a has-been. They found it a spot to hang around, but it's no longer part of the future plan. "Sorry programmers! Take a look at our new tools!"
| | VB is still around even though it looks an awful lot like C#. | unfortunately, converting VB6.0 code to VB .NET is a rocky road.
I meant VB, not VB.Net. The fact that you think of both as VB is a good example of Microsoft's attempt to kill VB. They have litle in common aside from language similarities. One's a COM-centric Windows programming tool. The other is a Java-esque wrapper sitting on top of windows. VB is currently still among the most widely supported tools for writing Windows software. Probably only VC6 can install on as many systems without needing support files installed. But VB has been *officially* unsupported for a long time now.
| MS even started giving away Express versions of Visual Studio that were | pretty much uncrippled to try to pique interest. |
Yes. I have VC8 Express for doing things like recompiling OSS. Even the OSS extremists grant grudging respect for Microsoft IDEs. :)
| > ActiveX at least has had a long run in IE | > and is still central to Windows. | | ActiveX sort of grew out of OLE 2.0 and COM. You wouldn't have to rent a | large auditorium to have a meeting of all the people who really | understood how COM worked. apparently the MFC developers wouldn't be | attending either. Of course COM had some complex and hideous hacks to | make it work with VB. ActiveX and its wizards sort of made life easier.
I guess we're getting into limited interest territory here, but as someone who loves COM I have to disagree slightly. ActiveX is COM, to begin with. (I have a book called The Essence of COM, from a cranky Harvard expert, who spends an entire, hilarious page detailing in almost techincal terms how ActiveX doesn't actually mean anything at all. :) COM is a bit of a debacle for C++ programming, but it's pure pleasure for VB. It's arguably the precursor of the current OO programming craze with endless classes:
Using System.This.That.TheOtherThing.OhAndThisThingToo
The nice thing about COM is that it's integral to Windows. The .Net framework is a vast wrapper of classes. Java is a vast wrapper of classes. COM is Windows wrapped in classes/objects. It's Explorer. It's IE. It's folder windows, toolbars, Explorer Bars, native controls....
| | The real problem was letting an ActiveX control run in a browser.
Yes. IE gave ActiveX a bad name. It should not have been COM compatible online, *because* COM is Windows. They should have made 2 browsers. One for online and one for offline. But of course no one thought about security issues back then. The only issue was to kill Netscape, and ActiveX helped a lot with that. At the time, ActiveX controls in a webpage were a very clever idea. (They still are, so long as it's offline. :)