[vinceguidry]

We're migrating an app from Ruby to NodeJS, and I keep hoping it'll get better, but everywhere I look, from the inconsistency and constant shifting of language semantics to the immaturity of the ecosystem, and how the former practically enshrines the latter, I can confidently state that Javascript is an objectively worse language. Attempts to solve problems caused by Javascript only make the whole thing worse.

At the moment, I actually prefer vanilla javascript to ES6-7. ES6 is inconsistent in awful ways. You still can't rely on bindings to stay put and new additions like the splat operator just don't work the same way all the time.

The more I learn JS, the more I hate it. I think eventually the web development community will come around, Node will lose mindshare, and compile-to-js languages will find their place in the sun again.

I suspect that people who actually like the language are experiencing a form of Stockholm Syndrome.

[epicide]

> I actually prefer vanilla javascript to ES6-7

ES6 is vanilla JavaScript. Most modern browsers have support >98% of added ES6 functionality for several major versions at this point. Admittedly, Node.js is still lacking, but it's getting there.

> You still can't rely on bindings to stay put and new additions like the splat operator just don't work the same way all the time.

Unless you have a bug to report about undefined or non-deterministic behavior, then it must be something you're doing. Random functionality is not intended behavior.

> eventually the web development community will come around... and compile-to-js languages will find their place in the sun again.

This is implying they were ever there. The big ones that come to mind were terrible. They would produce way more bloated frontends than anything we see today. In general, adding a layer of abstraction can be incredibly useful sometimes, but they can come at a steep cost.

What you include in "compile-to-JS" does get a little tricky to define, though. Things like TypeScript or even Babel can kind of count here. I think we will likely continue to see these, but I seriously doubt we'll see a resurgence of anything like GWT again.

> I suspect that people who actually like the language are experiencing a form of Stockholm Syndrome.

Sure, but the same can be said for anybody working with computers ;)

[vinceguidry]

> Unless you have a bug to report about undefined or non-deterministic behavior, then it must be something you're doing. Random functionality is not intended behavior.

You wouldn't be saying that if you ran into the behavior we have. Eventually I'll do more digging to find out root cause. But there's no way it was us.

> I seriously doubt we'll see a resurgence of anything like GWT again.

I'm thinking more along the lines of CoffeeScript. It bifurcates the landscape even further, but honestly I don't think it can really get any worse than it is now. But at least it will be building on top of sanity and not the lava layer.

[pjmlp]

I learned to embrace platform languages, regardless how I might feel about them.

Not having to deal with extra debugging layers, lesser debugging tools and additional manual FFI is much more productive than whatever I might gain in syntax/semantics of the "compile-to" language.

[sdegutis]

Node is identical to Ruby in all these ways. How man Ruby gems no longer exist that countless web apps used to depend on? How many backwards incompatible changes has Rails made?

[mellett68]

Were there any tech reasons for switching from ruby to node?

[vinceguidry]

Sadly, no.

[mellett68]

Thanks, I was just wondering since I don't really see the point in rewriting between dynamic languages. Aside from a few things being easier in each (async being an example) they're basically the same to me.