Isomorphic JavaScript: The Future of Web Apps

Post by ilaksh » Wed, Nov 13, 2013, 5:05 AM UTC

spion wrote: post #79

lucasjans wrote: post #60

Conspicuously absent from the author's article was Angular. What is it about Angular that doesn't lend itself to this dual purpose frontend and backend infrastructure?

Lots of potential hidden state as well as the need to support the entire DOM API server-side. For example, directives may add hidden state to the DOM and assume full availability of DOM API (even jQuery). The server will have to support all that Also, you'll have to re-do the entire rendering on the client, then swap the server-generated DOM with the client-generated DOM. Its probably possible - but is it worth the e…

Post by lennel » Wed, Nov 13, 2013, 11:33 AM UTC

peterhunt wrote: post #119

sitkack wrote: post #118

Earlier quoted context omitted.

In my scenario an alternative (Rhino or PhantomJs) engine would generate a page once and then push that rendered page to the server. No real load would be sent to it. Single code path for all template rendering. Zero cross implementation bugs and the client still gets a fully reified page on first load. Shit idea, lil harsh.

Shit idea is a little harsh for sure, but the problem is when your page relies on dynamic data and you can't prerender it. It's just too expensive to boot up a DOM on the server.