3 ms·
It would support the parent comment if the point of the parent comment had been something like "The state of the web has changed a lot since 2005," but it wasn'
by chc 6y ago
It would support the parent comment if the point of the parent comment had been something like "The state of the web has changed a lot since 2005," but it wasn't. The parent comment was specifically castigating the JavaScript ecosystem for having so much "churn" "because the people writing JavaScript do not know what they are doing." Ruby on Rails is not a JavaScript framework, so if there's been lots of change throughout the web ecosystem in same timeframe, how does showing the same trend reflect negatively on JavaScript developers in particular? It seems a bit like pointing to somebody in an earthquake and yelling at them to stop moving around.
- majormajor 6y agoYes, it was bad then, too. Doesn't seem like much of the Node ecosystem learned from that, though. Rails projects were pretty famously brittle and painful to deal with for doing major upgrades. I've moved to JVM-land and don't miss that part of working with Rails, though there are still things I miss about Ruby. But everything my coworkers tell me about Node projects sounds like it's even worse than Rails was.