I believe the JS criticism is more about the culture and ecosystem than the language itself. In short: Most if not all JS devs are more interested in playing wi

I believe the JS criticism is more about the culture and ecosystem than the language itself. In short: Most if not all JS devs are more interested in playing with specific tools and APIs rather than dealing with and/or implementing programming patterns and principles. In the last decade "small modules" skyrocketed the popularity of NPM and a lot of people pushed the idea of "don't reinvent the wheel just 'npm install' everything" and sadly it stuck. Basically all JS-related discourse reduces down to "use X instead of Y!". It started with packages, then libraries, then frameworks, and now meta-frameworks – hell even meta-meta-frameworks if you count the people raving about Blitz. It's like that period when young devs couldn't tell the difference between jQuery and JS but way worse. So yes, in a way you are in fact cheating your way out of software engineering by installing neverthrow or whatever. I mean the language is already pretty damn high-level already.