I don’t think we get it.
I don’t think we get it.
[Edit: Also, anecdote: before JS, I was mostly a C# developer, and the churn there was at least as bad, maybe worse in my personal experience. Over 15 years of my career, I had to learn ASP, then ASP.NET, and in the Windows app world, we went from WinForms to XAML, then .NET Core came out, and things shifted again... See Rails' history for more examples of churn. It's not like every other platform is a paragon of stability. Clojure is a bulwark of stability compared to just about anything else, but it's hardly fair to hold the front-end community up against that gold standard...]
I wouldn't re-write an existing app to use fetch or hooks, but now that I've taken the time to learn, I'm happy I did. The vast majority of the mental work was done by other people, and I get to reap the benefits. The alternative to this is stagnation, and relegation to legacy systems... I guess the author wishes they could work in COBOL?
Yeah it’s prevalent, and if we resemble other shitty ecosystems then we need to introspect.
I’m not entirely sure that churn is a binary good or bad. When you think, “Hm I have a more elegant solution to this common problem.” And then offer it to the world, you’ll be shot down with “churn” comments. Churn is way we experience experimentation and the slow progress towards a better solution. I, for one, am glad I no longer have to program COBOL.
Anyway, there’s probably a happy medium. Even Clojure has had some front-end churn. Om is no longer the hotness. Reframe seems to have won. Clojure itself isn’t that old.
None of you make your own landscape easy to enter, and I’m certainly not open to you guys dictating anything in this realm.
We have frontend churn, we are working on it.
You didn’t work on dot net churn while it was occurring, and you show up with the same attitude before the apex on front end. You couldn’t stop it once, and you’re here to enable the next?
If you know how to stop it, talk. Otherwise stay out of it.
We’re trying not to become you.
The whole Apple client-dev ecosystem is still in the process of changing to Swift, and Apple is trying to develop SwiftUI into a compelling layer alongside/atop {App,UI}Kit. It's not just a web/JS challenge.
Client dev is always changing.
Frontend is knee deep in the process of creating cargo cult devs en masse, and I’m depressed by all of this.