Matestack – Reactive UIs in pure Ruby

Re:Matestack – Reactive UIs in pure Ruby by aerovistae on Sunday November 22, 2020 @11:48AM (#25178826)

I don't really see too many companies or projects using node on the back end. It's pretty hard to buy that node replaced rails. I see a lot more Java than anything else.

[ Parent | on HN ]

Re:Matestack – Reactive UIs in pure Ruby by pdoub on Sunday November 22, 2020 @01:38PM (#25179783)

A lot of companies I'm speaking to (mostly Berlin/Germany based startups) have drank the "we have to use JS on the frontend anyways, and by going fullstack JS we can reduce our payroll since we can focus on only hiring JS devs and they magically work on ReactNative, the React web app and the Node.JS backend at the sime time" koolaid. Works super well for some, less so for others...

Edit: Explicitly added Node.JS since that's what they rave about for making it possible.

[ Parent | on HN ]

Re:Matestack – Reactive UIs in pure Ruby by cutler on Sunday November 22, 2020 @01:05PM (#25179493)

That's because Java is one of the top 3 adopted languages and is general purpose. A more relevant comparison would be between Node.js and Django, Rails or Laravel and as far as job stats go, eg. https://indeed.com, Node.js is everywhere.

[ Parent | on HN ]

Re:Matestack – Reactive UIs in pure Ruby by jozzy-james on Sunday November 22, 2020 @02:32PM (#25180295)

i think it really depends on the industry - mine for example, most of the bigger players are running express apps on the FE (not 100% sure on backend, seems a mix of go/node and other things) - but why bother to run express/node on the frontend if you're not also going to leverage it on the backend.

[ Parent | on HN ]