Microsoft Killing .NET?

I’ll first link to the following posts:

http://developers.slashdot.org/story/11/08/03/2027207/Was-NET-All-a-Mistake
http://www.i-programmer.info/professional-programmer/i-programmer/2830-was-net-all-a-mistake.html
http://www.i-programmer.info/professional-programmer/i-programmer/2591-dumping-net-microsofts-madness.html
http://www.i-programmer.info/professional-programmer/i-programmer/2465-classic-vb-is-20-and-still-missed-by-many.html

The only comment I have (other than the proverbial “I told you so” RE: Microsoft’s so-totally-planned obsolescence for .NET) is that Delphi is still as low-level and powerful as C++ and still as easy and high level as Visual Basic.

Nobody needs to go back to MFC or VC++…they need to wake up and realize its time they left the Microsoft camp for good.

I am certainly glad none of MY competition is aware of what can be done in Delphi 🙂

7 Replies to “Microsoft Killing .NET?”

  1. I do not think Microsoft has ever indicated they are dropping .NET support. Those links that you are sharing are all based on unfounded rumors as far as I know; they were based on an early demo of Windows 8 wherein the person performing the demo indicated that HTML5 and JavaScript were a supported development platform. There was no indication that HTML5 and JS were in any way a preferred development platform, nor was there an indication that the .NET platform was to be deprecated.

  2. Also, it seems weird to me that you are advocating leaving Microsoft in favor of Embarcadero since it then boils down to leaving one vendor in exchange for another vendor. The last link you shared (wherein the blogger is sharing about how VB6 is still missed by many) states that, “The story of classic Visual Basic is one worth knowing if only to warn of the dangers of adopting a technology that comes from, and is under the control of, a single source.” Well, Delphi is in the same boat, it comes from Embarcadero is under the control of Embarcadero.

    Please do not get me wrong, I love Delphi, I think it is a very powerful development framework and it is a shame that it is not in greater use. However, the dangers of vendor lock-in are equally present with Embarcadero as it is in Microsoft.

  3. You raise a good point!

    I guess though part of what I am trying to say is that Microsoft is definitely unique, even among other vendor-lock-in scenarios. They carry more risk above and over the standing risk of a vendor lock-in.

    Again, comparing with Delphi: no product has been so abused, so mismanaged, so badly marketed (oh wait maybe InstallAware ;)) as Delphi. Yet it has still survived and it still offers the best native code development solution on Windows, with unmatched levels of compatibility across almost two decades of production. Can you say the same of MFC? VB? WinForms? WPF? Silverlight? It keeps going and going…are developers really happy that everything is radically changing so fast with no real tangible benefit?

    Microsoft and their seeming strategy of “Planned Obsolescence”: The fact is Microsoft is in a position to, and as such will always be tempted to, abuse its monopoly on the PC market. However they maybe betray their significant weaknesses on this platform when they decide to HTML5/JS everything, in panic from competition that is emerging on brand new platforms that are opening up the ultimate utility of the PC into question again for the first time since the 90’s! Think iPad, iPhone, i*; we’re a long ways from the days when Windows XP was really cool. I’m sure Apple & friends are extremely happy that NT 6.x turned out so poor right on the eve of their major new push forward.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.