Does this mean Rendrjs applications will run in a JavaScript disabled browser? That would be a big win!
Re:We've Open-sourced Rendr
by frontendbeauty on Friday April 19, 2013 @01:02PM
(#5577605)
Yep! Because links use full URLs which get intercepted by JavaScript, if JS is disabled, you can still navigate around the app, getting full HTML from the server. Of course, any client-specific code wouldn't run (slideshows, etc).
So far, this is the most convincing argument I've heard for Rendr.
I'm a little confused here. Maybe I'm just not seeing it, but how does that make Rendr any different from any other server-side framework that responds with HTML?
Re:We've Open-sourced Rendr
by WickyNilliams on Sunday April 21, 2013 @01:23PM
(#5585509)
Because you're using the same JavaScript code for rendering on either the client or the server.
How do you measure performance? I'm interested specifically in where & how you instrument, and how you collect the data.
EDIT: We decided against using something like PhantomJS or node-chimera because why deal with a DOM if you don't have to? DOM is complicated and slow, compared to string-based templating. Plus, it's another moving part, another process to keep up and running. The Meteor guys aren't too excited about the PhantomJS approach either, and IIRC they'd like to be able to serve HTML without firing up a DOM.