| People writing these kind of articles are really not looking at their current stack objectively. If I'm doing backend, I have to pick from various languages, I often will still need build tools (often more complicated) for various reason), you need to spin up a server (or make an AWS account....maybe use S3, maybe not!), you still have dependency management, etc etc. Remember when Maven picked up, the bitchfests that surrounded it? And debugging a server side app in production by picking at memory dumps, profilers, etc? Its not exactly easy. The difference is that those problems are understood, and everyone knows the barrier for entry is higher. The web platform used to feel like it had a low barrier for entry because it was so limited and there was only so much you could do. Those barriers were removed, so now its just as hard as anything else, except its not quite as understood (the barriers were removed recently). So all of the peanut gallery goes in thinking they can change the world in JavaScript, then realize they actually need to learn to engineer. A good example of that problem is all of the big companies and startups hiring "full stack" engineers, which is code name for "pure backend engineer who has 10+ years of experience doing backend...and has heard of HTML". Of course, that kind of people won't go far. |