Live data from Hacker News

Isomorphic JavaScript: The Future of Web Apps

nerds.airbnb.com

41–50 of 123 posts

Re: Isomorphic JavaScript: The Future of Web Apps

#41
post #21

this is interesting so Javascript can now be used for server-side which removes the need for Ruby on Rails and Django basically? can someone summaries this article, time is of the essence.

If you're not familiar with server side javascript, looking up node.js is a good place to start.

Re: Isomorphic JavaScript: The Future of Web Apps

#42
post #4

We do this sort of thing on the site I work on, Google+. Initial page-loads are rendered on the server, subsequent page-loads are rendered on the client. Really good for performance. It's just the templating system that's common code, though, the server is still Java.

(author) Cool! What's the JavaScript runtime on the server? Something JVM-based?

The server code is still Java, but our template language (https://developers.google.com/closure/templates/) compiles to both JS and Java.

Re: Isomorphic JavaScript: The Future of Web Apps

#43
Wasn't this the idea with GWT so many years ago? In GWT's case, it was Java on both sides. I don't believe that it solves the problem and I don't believe Javascript on both sides will solve the problem.

This is a classic "impedance mismatch" like O/R mapping. At the end of the day, there may be no good, i.e. simple, solution. It is inherently difficult and messy.

Re: Isomorphic JavaScript: The Future of Web Apps

#44
post #42

Earlier quoted context omitted.

(author) Cool! What's the JavaScript runtime on the server? Something JVM-based?

The server code is still Java, but our template language ( https://developers.google.com/closure/templates/ ) compiles to both JS and Java.

Why not render the templates in PhantomJs and have a user account that can push the rendered template back into the server cache. No need to duplicate the work of writing two backends. Or hell, just use Rhino and generate the reified pages on the server.

Also, you can't patent this now.

Re: Isomorphic JavaScript: The Future of Web Apps

#45

You keep using that word. I do not think it means what you think it means. Using precisely defined mathematical words in contexts where they only make sense vaguely to a layperson ruins their original usage. Make up a new word. Repurpose a shitty English word. But leave our damn maths words alone. Old man quarterto shakes his fist at you! Get off my smooth, compact lawn!

isomorph(ism) is actually from chemistry, not mathematics.

Re: Isomorphic JavaScript: The Future of Web Apps

#46
post #45

You keep using that word. I do not think it means what you think it means. Using precisely defined mathematical words in contexts where they only make sense vaguely to a layperson ruins their original usage. Make up a new word. Repurpose a shitty English word. But leave our damn maths words alone. Old man quarterto shakes his fist at you! Get off my smooth, compact lawn!

isomorph(ism) is actually from chemistry, not mathematics.

[deleted]

Re: Isomorphic JavaScript: The Future of Web Apps

#47

You keep using that word. I do not think it means what you think it means. Using precisely defined mathematical words in contexts where they only make sense vaguely to a layperson ruins their original usage. Make up a new word. Repurpose a shitty English word. But leave our damn maths words alone. Old man quarterto shakes his fist at you! Get off my smooth, compact lawn!

Actually mathematics got it from chemistry: http://en.wikipedia.org/wiki/Eilhard_Mitscherlich

Before maths, it was probably mostly geologists that used it. It's also used plenty in evolutionary biology, but this was probably after maths (not sure though).

Re: Isomorphic JavaScript: The Future of Web Apps

#48
post #45

You keep using that word. I do not think it means what you think it means. Using precisely defined mathematical words in contexts where they only make sense vaguely to a layperson ruins their original usage. Make up a new word. Repurpose a shitty English word. But leave our damn maths words alone. Old man quarterto shakes his fist at you! Get off my smooth, compact lawn!

isomorph(ism) is actually from chemistry, not mathematics.

But in the end, isn't everything math?

longingly gazes into the distance

Re: Isomorphic JavaScript: The Future of Web Apps

#49

I'm having a brain freeze here. How do you render a DOM on the server and then push it out to the client? Convert in memory DOM to a text/html representation before sending?

You could use something like Phantom JS. To iterate a point in the article, a number of client-heavy sites built on Angular and Ember have been rendering their content on the server-side to be presented to crawlers like the Googlebot for SEO purposes.

I understand node.js with V8 and also Phantom JS but how does a client browser view the DOM rendered on the server is what I'm asking. I'm guessing it gets rendered and serialized to JSON for transport, but I could be over-thinking it. Server side rendering is the same as it ever was, just with new tools.

Re: Isomorphic JavaScript: The Future of Web Apps

#50
post #45

You keep using that word. I do not think it means what you think it means. Using precisely defined mathematical words in contexts where they only make sense vaguely to a layperson ruins their original usage. Make up a new word. Repurpose a shitty English word. But leave our damn maths words alone. Old man quarterto shakes his fist at you! Get off my smooth, compact lawn!

isomorph(ism) is actually from chemistry, not mathematics.

It's from Greek, really. It's used in both chemistry and mathematics.

http://mathworld.wolfram.com/Isomorphism.html

Post reply on HN