[hrdwdmrbl]

You're right about Node, but I think it's a bit apples to oranges because they're suited to different use-cases. Rails is great for mostly static sites. Node is great for mostly dynamic sites. It's almost as simple as that.

[cutler]

Whilst Node and Rails certainly have different niches the distinction between static and dynamic sites is lost on me. Both are written in dynamically-typed languages and both produce HTTP responses dynamically. What's the basis of your Rails = static sites assertion?

[hrdwdmrbl]

I didn't literally mean static sites ️ By static I mean I site like Github, Craigslist, Wikipedia. Stuff doesn't change often. Uses forms for submitting data. By dynamic I mean sites that make heavy use of ajax, you want real-time anything, high levels of interactivity in the interface. These are often apps.

[cutler]

Rails has an --api option and most of the Rails roles offered by recruiters these days are a combination of Rails and React, Vue or Angular. Rails assets are served with webpack and there are options for React, Vue and Angular when creating a new Rails app.

[hrdwdmrbl]

Yes but Rails is still optimized for REST CRUD apps. It's great at those apps. I use it to develop those kinds of apps. But when you want something super reactive and customized and interactive and dynamic and real-time, I reach for Node.

[cutler]

If I wanted something super reactive, truly concurrent and real-time there are many better options than Node - Elixir, Golang and Clojure to name a few. I just don't get the Node hype - it's not the best tool for anything other than allowing JS devs to pass themselves off as back-end experts.

[wolco]

If the site is static you only requre html files. A server side language like Rails would only be used to create dynamic sites.

[hrdwdmrbl]

No that's not what I meant.