News for hackers. Stuff that matters.
Re:Isomorphic JavaScript: The Future of Web Apps by sitkack on Monday November 11, 2013 @08:13PM (#6715241)
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 by lennel on Tuesday November 12, 2013 @01:25AM (#6716198)
The soy templates have a java (tofu) backend already (several years old).

The phantomjs idea is a shit idea and should go away. Phantom is fine and good for headless testing (hells we use it for quite a bit else) but seriously it is not a solution for a real load.

Re:Isomorphic JavaScript: The Future of Web Apps by sitkack on Tuesday November 12, 2013 @02:17PM (#6720171)
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.

Re:Isomorphic JavaScript: The Future of Web Apps by peterhunt on Tuesday November 12, 2013 @03:28PM (#6720743)
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.
Re:Isomorphic JavaScript: The Future of Web Apps by lennel on Wednesday November 13, 2013 @06:33AM (#6724533)
Why would you pre-render if your data is not changing continually? Don't you just have static content then?