4 ms·

This is obviously a pretty common belief, but I do think web dev gets held to a weird standard when framed as "the one with too much tech churn". Just because

This is obviously a pretty common belief, but I do think web dev gets held to a weird standard when framed as "the one with too much tech churn". Just because someone solves a problem with a new library or framework does not mean they solved a problem for all of web development, and I think the current concentration of applications made with boring things sort of reflects that. [0] > developers are rewriting their app in whatever the new framework is. That is obviously an over-exaggeration. Most devs, most teams, most companies are not open to rewriting any application ONLY because it's a new framework. If they are, they probably have other priorities that point at X framework/library when rewrites do happen, because a rewrite is big enough already without having to also create the pattern/library code. I will absolutely agree that we ignore the user more than we should. That should change. But I think people being excited about something on HN or some other metric of "a new framework every 6 months" isn't as causative as the usual hive mind would imply. [0] https://www.statista.com/statistics/1124699/worldwide-developer-survey-most-used-frameworks-web/ https://www.statista.com/statistics/1124699/worldwide-develo...

ehutch79 2y ago
It's a lot better now, but there was absolutely a period when it felt like there was a new framework/library weekly. This was 5-10 years ago. 'Cambrian explosion' was the term going around. A lot of it was in react space, with router libraries or the newest data store being the thing you needed to be using. Definitely turned me off react, personally at least. The angular.js/angular2 migration was also a big pain around this time as well. There was a lot of social pressure from influencers on youtube and various social media that you NEEDED to switch now. This was the new hotness, it was blazing fast, anything else was obsolete tech debt. There was one instance of 'or you should be fired' that sticks with me. I think we're just used to the hyperbole and are all a lot more jaded now. Compare this to the backend, where django, rails, and the others haven't really changed. I haven't felt the need or pressure to rewrite my views/controllers/whatever at all.
- crabmusket 2y ago
  > There was a lot of social pressure from influencers on youtube and various social media that you NEEDED to switch now I wish I had something more coherent to say about this, but: I think this is true, and it frustrates and saddens me that anybody took seriously what influencers on youtube had to say. It seems so obvious that they are there to get views, but even beside that, that they don't know anything about my app or the problems my users have.

ehutch79 2y ago

It's a lot better now, but there was absolutely a period when it felt like there was a new framework/library weekly. This was 5-10 years ago. 'Cambrian explosion' was the term going around. A lot of it was in react space, with router libraries or the newest data store being the thing you needed to be using. Definitely turned me off react, personally at least. The angular.js/angular2 migration was also a big pain around this time as well. There was a lot of social pressure from influencers on youtube and various social media that you NEEDED to switch now. This was the new hotness, it was blazing fast, anything else was obsolete tech debt. There was one instance of 'or you should be fired' that sticks with me. I think we're just used to the hyperbole and are all a lot more jaded now. Compare this to the backend, where django, rails, and the others haven't really changed. I haven't felt the need or pressure to rewrite my views/controllers/whatever at all.

crabmusket 2y ago
> There was a lot of social pressure from influencers on youtube and various social media that you NEEDED to switch now I wish I had something more coherent to say about this, but: I think this is true, and it frustrates and saddens me that anybody took seriously what influencers on youtube had to say. It seems so obvious that they are there to get views, but even beside that, that they don't know anything about my app or the problems my users have.