the big advantage with having the same language on both ends is being to use ser... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		marcus_holmes on Oct 4, 2016 \| parent \| context \| favorite \| on: Hyperloop – The Missing Ruby Front-end Library the big advantage with having the same language on both ends is being to use server-side rendering (isomorphic). So your first page serve includes the initial rendering of the content, and then the client-side code takes over to handle changes with no refreshes. If the client is written in a different language than the server then you have to maintain two versions of the page code to achieve this, and they have to be in perfect sync. Hard to do. Easier to write the code once and transpile to JS for the browser (or write the back end in JS).

michaelmior on Oct 4, 2016 [–]

Not necessarily. You can use something like Prerender[0].

[0] https://github.com/prerender/prerender

marcus_holmes on Oct 5, 2016 | [–]

but... that only renders JS... which is what the client speaks, so the client and server still speak the same language

michaelmior on Oct 5, 2016 | | [–]

Your backend can run whatever language you want. There are examples right on the page that show integration with Rails, PHP, Go, and others.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact