5 ms·
If you group it like that, then there is a whole graveyard of Node and JS technologies that have died along the way, too. Ember.js, AngularJS, Knockout.js, Bac
by CharlieDigital 3y ago
If you group it like that, then there is a whole graveyard of Node and JS technologies that have died along the way, too. Ember.js, AngularJS, Knockout.js, Backbone.js, etc. Waaaaay more than Microsoft's go at it.
I'm not even sure why you're counting WebAPI in there since it's for writing REST APIs.
- pjmlp 3y agoI guess because writing Web FE with a .NET backend is something that many .NET developers happen to do, via WebAPI exactly. The graveyard of Node and JS technologies is orthogonal to the current burnout feeling in many Windows circles regarding Microsoft technologies. To the point that, as I already mentioned a few times, I happened to do .NET Framework to something else ports, instead of the more rational migration to modern .NET. You see the same in long time well known Microsoft partners like Sitecore, moving away from .NET.
- CharlieDigital 3y agoFeels like moving goalposts here. Technologies change all the time in every stack; flavors come and go. By the standard of the web JS ecosystem, .NET has been relatively stable.
- pjmlp 3y agoMy goalposts are still the same, Microsoft FE frameworks since the dawn of time, Web and native, and their continuous replacements, when the team doesn't meet whatever KPIs. I don't care what others do. It is like kids on the kindergarten playground, arguing for who behaves better.