I'm sick of this lie, mostly parroted by people that haven't touched frontend in their life, or who do frontend but betted too early on technlogy that never got

I'm sick of this lie, mostly parroted by people that haven't touched frontend in their life, or who do frontend but betted too early on technlogy that never got traction. It feels like it's just an excuse to pick on frontend. If nothing new was developed everyone would point out how stagnant JS ecosystem has become. I've been developing JS for years and I've been using NPM for frontend components for... 3 years minimum? Wow, such a quick pace, unbearable. How is it bad that new tools and libraries are being developed? Nobody forces you to use the new shiny toys until they're established (and almost nobody does, unless you can afford the uncertainty). You call it churn, I call it advancing the trade and getting better tools made for free by passionate people. Some of those get established as de facto standards. Most don't. The churn rate is not high unless you count experimental technology. > That something using Bower can be considered old really seems quite astonishing to me. Bower was one of those shiny toys. It's not old: it's just that people used Bower on its infancy and it never got as much traction as NPM did. If someone bets on Bower and then blames churn rate when it gets less traction than competitors... maybe they should stop using the new shiny toys and wait until an established tool emerges?