4 ms·
I still remember the uproar when .NET was first announced, and how it was widely predicted it would utterly fail, and people who couldn't understand why anyone
by wccrawford 15y ago
I still remember the uproar when .NET was first announced, and how it was widely predicted it would utterly fail, and people who couldn't understand why anyone would use it.
IT evolves constantly, and you have to stay with it. Getting upset about it changing is pointless and being stuck on 1 technology will quickly see your business left behind.
- 51Cards 15y agoCouldn't agree more. I was also in the thick of things when .NET came out. We had a large established base of apps on the pre-existing versions of Visual Studio. The whole migration nightmare/uproar to .NET is still fresh in my mind and I clearly remember how the .NET supporters fundamentally said "Time to move on". Small bit of irony that now (in some cases) time to move on applies to .NET itself. (though I wholeheartedly agree that most of this uproar is silly, .NET is much more robust and flexible than HTML5 and not in any danger of being "replaced") Still brings a small smile to my face though when I see .NET developers upset about no viable migration path forward. This cycle will repeat again in X years, it's the nature of the biz. Most of our careers are going to span several major shifts in technology and you just roll with it.
- ern 15y agobeing stuck on 1 technology will quickly see your business left behind Or your career. I know of a couple of VB6 developers who stopped coding after .NET displaced it.