[hardwaresofton]

I actually made that statement with the pace of the front-end world taken into account -- ember actually churns additionally :( . Part of Ember's openness to doing things better often involves deprecating/removing parts of their API that they're convinced was wrong before -- it's not a bad thing, but it means that if you get stuck on some version, and the next version has gone a different way on some concept/part of the framework, you're going to have a bad time, even if the landscape hasn't moved much yet.

I spend a lot in frontend land and I've grown somewhat accustomed to it's insanity. I actually even like it at this point -- Let everyone go insane in all the different directions, watch how they fare, then let the good stuff rise to the top, and pull out the interesting paradigm shifts if there are any. Platforms like C# often have a lot more enterprise weight behind them and "stable" takes on a completely different meaning.

I might even say that churn in .NET is happening too, it's just way way more localized. For example the .NET core/standard move is happening right now, but I can only assume that the vast majority of codebases on .NET 4.x don't care at all, and are letting it work itself out maybe over the next year before they even consider moving (if they ever move at all). As a person who's struggled with porting a .NET 4.x package to .NET core/standard, and with some associated libraries (EF, mostly), it was not a pleasant experience, but by the time it gets to everyone else, it probably will be.