Could there be a feature to run the app logic on the client when a connection is not available? Else, it can fallback to the server. This will help a lot when it comes to offline support
We've Open-sourced Rendr
51–56 of 56 posts
Re: We've Open-sourced Rendr
#52I'm not sure I fully understand this, is this just for SEO? Why not run the page in phantomJS, which is what we do at https://circleci.com , and what meteor apps do, and any others?
Or Zombie, which is way faster than PhantomJS: https://github.com/bfirsh/otter
Re: We've Open-sourced Rendr
#53Earlier quoted context omitted.
Care to explain? They use pushState or hashes for routing, and load data via XHR. If you are using pushState it is assumed that the URL must exist on the server.
Having the URL exist on the server isn't the same as serving a rendered page from the URL, which is what most SPAs do. You could just rewrite all URLs in a website to point back to your index.html, then have the client side router initialize the app from the URL parameters. If you don't have javascript turned on (e.g. googlebot) then all you'll see is a blank page
Googlebot interprets javascript. In that case you shouldn't use pushState but fragment URLs[1].
I should have said it is assumed that the URL exists on the server and points to the same resource/content; otherwise setting URLs using pushState makes no sense. GitHub is a good example of how it should be done, not an exception.
[1] https://developers.google.com/webmasters/ajax-crawling/docs/...
Re: We've Open-sourced Rendr
#54Earlier quoted context omitted.
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
#55Earlier quoted context omitted.
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?
Because you're using the same JavaScript code for rendering on either the client or the server.
Re: We've Open-sourced Rendr
#56Wow, looks very impressive from my quick look over it. These days, there are so many JavaScript frameworks for web development, it's starting to make my head spin a little bit. Does anyone have a link to a good rundown of where everyone stands?
Being a JS developer must be the pits - you need to run really fast just to keep up.
...you need to run really fast just to keep up.
This is exactly the part of being a JS developer that is appealing :)