3 ms·
It is a lost cause to rationally try and sort out what if anything is chronically wrong with js, ruby, haskell, c (or any language of choice). They each have th
by stareatgoats 5y ago
It is a lost cause to rationally try and sort out what if anything is chronically wrong with js, ruby, haskell, c (or any language of choice). They each have their pros and cons, and have evolved differently for different reasons. Since programming languages many times (seemingly) are like a dear spouse to its disciples such discussions generally devolve into endless and meaningless comparisons, if not worse.
The article obviously panders to ruby sentiments, and the javascript experience can obviously be frustrating to that community, as might ruby to a mainly javascript developer. Might we just leave it at that?
- jspash 5y agoI think the big difference with JS is that if you're doing just about anything in Web Dev these days, you MUST use JS (with a few exceptions). Don't like PHP? Try Python. Why not Go, Scala or Rust? Don't like Ruby? Move to Elixir (no really, do it! you won't regret it) But with JS you're stuck with JS - at least Typescript makes things a bit more sane. So until the browser monopoly ends and something supplants JS as one of the only ways to make a dynamic website, it will have to take the heat. The best experience I've encountered is with LiveView in the Elixir/Phoenix world. It still needs JS for the plumbing (websockets) but I no longer have to write JS. Happy days!