i have a confession
i actually kinda like JS. if you leave out inheritance, program in a pseudo-functional style, and don't get distracted by the 500 new frontend frameworks and build tools that come out every week, you can be super productive in JS.
i think JS gets a lot of hate because it kinda sucked for a long time, but it sucks a lot less now.
but i have no real-world use case for haskell, clojure's dependency on the jvm is a PITA, and python is really well-designed but the ecosystem is confusing (python 3 came out TEN YEARS AGO and i still never know which version of python to use in any given project!).
@zacanger It did a lot of good, IMO it played a significant role in popularizing first-party async features in languages (and higher-level parallelism abstractions than plain threads).
(but I still don't really like JS because of a lot of the fundamental design decisions are frankly asinine)
@besserwisser i've never read that, but i probably should at some point, i know that's a very popular series.
a lot of the legacy frontend code i run into is like that: "here's a library, copy and paste this stuff, don't bother learning the language, just copy-paste this example"
@zacanger I don't hate JS because of its feature set or its 666 different frameworks that exist for other reason than that HTTP POST just isn't good enough any longer.
@lanodan i kind of agree, though i don't think there's anything wrong with using libraries/frameworks, because folks who actively avoid them seem to end up accidentally writing their own.
i do agree that the web can mostly be simpler, but at some point you're just trading client-side rendering for server-side rendering. for applications, all the complexity has to live somewhere. it's nice to say "i don't want my browser doing the work, your server should do the work" but that's not always easy