3 ms·

I’m not sure if you realize your own paradox. Is churn really so prevalent? You then point out how prevalent it is in the .NET community. Yeah it’s prevalent,

• christophilus 6y ago
  I do realize it. Maybe I should have added: churn as compared to what? JS doesn’t exist in a vacuum. Most language ecosystems experience churn. I explicitly mentioned we shouldn’t hold everyone to the gold standard of stability that is Clojure. But... maybe we should? 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.
  • deleted 6y ago
    [deleted]
  • runawaybottle 6y ago
    I’m waiting for the day I can enter a dot net C# codebase the same way you can enter frontend. 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.