I mean, from the outside I get it. For a very long time I avoided frontend jobs because JavaScript did suck. And I'd say that JavaScript-as-it-was--not writing

I mean, from the outside I get it. For a very long time I avoided frontend jobs because JavaScript did suck. And I'd say that JavaScript-as-it-was--not writing ES6, not polyfilling browsers, not using a sane framework--sucks today. These days I write pretty exclusively NestJS serverside and React/React Native on clients, using TypeScript through the whole stack and Swagger-generated clients for plumbing, and it definitely no longer sucks. But I had to 1) have a reason to get into it, and 2) spend a ton of effort to weld together a consistent environment that values developer time. There probably is too much nonsense going on at any one point in the JavaScript ecosystem. I mostly work in infrastructure/devops roles, where it's just expected that you know ten thousand little things that are arbitrary and stupid but will eventually bite you; having to hold an entire stack in my head and understand how to pivot and manipulate it is kind of what I do everyday, but it's not a standard programmer skill. If you don't have somebody who can do that--and it's a mixture of human communication and empathy, technical skill, and a certain kind of technical taste, so it's not as common as one might like--I still, today, see why somebody might say that JavaScript sucks.