2 ms·
One problem I see is that a lot of that page generation being moved to the client increases the first time page loads (which matter) and on a mobile device can
by zanny 14y ago
One problem I see is that a lot of that page generation being moved to the client increases the first time page loads (which matter) and on a mobile device can prove very taxing on 3 - 4 year old hardware.
I think it is more about do you want to figure out the html in JS or something else, and do you want to pay the bill to make the pages at home or lose some customers who don't have the power to do it themselves.
- andrzejkrzywda 14y agoIt's not all or nothing. You can do what Twitter did. Allow some duplication and render html server-side on the first request.
- hunvreus 14y agoAirbnb mentions that in a recent post: http://nerds.airbnb.com/weve-launched-our-first-nodejs-app-to-product http://nerds.airbnb.com/weve-launched-our-first-nodejs-app-t.... I think, ultimately, it depends on how your app is structured and how heavy is your feature set. We usually try and keep things as simple as possible, but we've experienced the issue a couple more complex apps and spent a good deal of time optimizing things and dynamically loading dependencies. They ain't no silver bullet: you have to decide where you want to invest your time.