Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Exaaaactly. I worked on big systems at a very large retailer, and at a very large bank, and in each case, there were reasons why GraphQL worked very well for us. But 90+% of developers across the world adopt tools and technologies because they look fun and shiny, not because they need it. For the overwhelming majority of developers (who in most cases are working at medium-to-large-sized companies on internally-facing apps with a small number of users) a simple web app stack from 2005 will serve you quite nicely.


I wonder if this phenomenon happens in other industries as well.

I can't imagine a road crew getting away with spending an extra year to build a road because they decided to use completely nonstandard equipment that doesn't work well for the task or they don't know how to operate. I especially can't imagine the road crew screwing up multiple jobs in a row because they change equipment every time they're starting to understand the current equipment.

Maybe it does happen though and I just haven't seen it since I'm not in that industry.


I don't know about construction, but as a farmer it's pretty natural to look at what your neighbours are doing and if they adopt a new technology in their operation you're at least going to give some thought to doing the same.

But I think it comes with a lot more reluctance and skepticism. You are not likely to jump in head over heels, and even when you do give it a try I expect most farmers will do so with the attitude of "if it doesn't work at least I can always go back to the old way".

The "OMG this is amazing and will solve all of my life's problems" attitude I see in tech certainly isn't there in my experience.


Construction is always the wrong metaphor for sw dev.

Think more like marketing campaign or product design.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: