4 ms·

.NET has a long life ahead of itself in the enterprise, where companies on "the Microsoft stack" typically won't even use 3rd party libraries where there is a M

.NET has a long life ahead of itself in the enterprise, where companies on "the Microsoft stack" typically won't even use 3rd party libraries where there is a Microsoft sanctioned alternative. Until Microsoft comes out with a replacement for things like Windows services and web application development, .NET will be around. I don't see there being an alternative even on the horizon. Presumably they could create a Node.js type of platform backed by Chakra but there aren't any signs that they are even working on such a thing. (Also, throwing out .NET would mean throwing out F# which gives them a lot of cred in certain circles).

powertower 13y ago
And also on the Desktop of every Windows OS, since .NET for-the-most-part is the new Windows API - an abstraction layer that sits and manages the older Win32 API (yes, it's also a few other things – framework, library, runtime, etc). The author of this peace works on making games. Hence why she thinks .NET is "dying". Her reasoning (points) have little to nothing to do with her argument and just seem to be there to help influence the clueless readers and to collect those that have agendas or chips on their shoulders (80 up votes for this delusional blog post).
eduardordm 13y ago
Keep in mind that .NET is relatively new to the enterprise and lots of those companies didn't even get out of cobol yet. Opinion: Timing is a important factor here. My bet is those enterprise companies skipped the .NET/JavaEE era and will jump right into what is coming next. I know a couple of banks that are heavy Adabas/Natural users for decades. When .NET/JavaEE boomed they opted to just wait. Now, no single framework can really solve most of your problems. In fact, the problems are so heterogeneous that using frameworks at all is becoming completely irrelevant. That said, .NET, JavaEE, Rails, Django, they are all dead to a certain point. What we will see is the rise of the non-frameworks. People will start doing their own stuff on Go (or anything else) and maybe will start open sourcing parts of it. You will have a lot of mini libraries that you will put together to fit your needs.
- marcosdumay 13y ago
  > You will have a lot of mini libraries that you will put together to fit your needs. Like a framework?
- MatthewPhillips 13y ago
  I disagree, many if not most cities in the East coast have been dominated by .NET since at least .NET 2.0. There are cities where it is hard to find a programming job in anything else. And the holdouts are mostly old Windows-centric tools like Delphi and VB6. I also disagree with your outlook for the future. Enterprise loves frameworks only slightly less than they love expensive proprietary software packages where support is built-in. I'd love to see non-Microsoft tech like Go move into the enterprise in a serious way but I don't see it happening. For most of these companies their developers have no experience in anything but the Microsoft stack and a good portion of them either can't or won't learn something else. So you're immediately talking about losing a large chunk of your staff. And good luck finding Go developers. I can't see Microsoft abandoning this segment so it doesn't make sense to even talk about alternatives.

powertower 13y ago

And also on the Desktop of every Windows OS, since .NET for-the-most-part is the new Windows API - an abstraction layer that sits and manages the older Win32 API (yes, it's also a few other things – framework, library, runtime, etc). The author of this peace works on making games. Hence why she thinks .NET is "dying". Her reasoning (points) have little to nothing to do with her argument and just seem to be there to help influence the clueless readers and to collect those that have agendas or chips on their shoulders (80 up votes for this delusional blog post).

eduardordm 13y ago

Keep in mind that .NET is relatively new to the enterprise and lots of those companies didn't even get out of cobol yet. Opinion: Timing is a important factor here. My bet is those enterprise companies skipped the .NET/JavaEE era and will jump right into what is coming next. I know a couple of banks that are heavy Adabas/Natural users for decades. When .NET/JavaEE boomed they opted to just wait. Now, no single framework can really solve most of your problems. In fact, the problems are so heterogeneous that using frameworks at all is becoming completely irrelevant. That said, .NET, JavaEE, Rails, Django, they are all dead to a certain point. What we will see is the rise of the non-frameworks. People will start doing their own stuff on Go (or anything else) and maybe will start open sourcing parts of it. You will have a lot of mini libraries that you will put together to fit your needs.

marcosdumay 13y ago
> You will have a lot of mini libraries that you will put together to fit your needs. Like a framework?
MatthewPhillips 13y ago
I disagree, many if not most cities in the East coast have been dominated by .NET since at least .NET 2.0. There are cities where it is hard to find a programming job in anything else. And the holdouts are mostly old Windows-centric tools like Delphi and VB6. I also disagree with your outlook for the future. Enterprise loves frameworks only slightly less than they love expensive proprietary software packages where support is built-in. I'd love to see non-Microsoft tech like Go move into the enterprise in a serious way but I don't see it happening. For most of these companies their developers have no experience in anything but the Microsoft stack and a good portion of them either can't or won't learn something else. So you're immediately talking about losing a large chunk of your staff. And good luck finding Go developers. I can't see Microsoft abandoning this segment so it doesn't make sense to even talk about alternatives.