6 ms·
What does "performance orientated" mean?
by bahador 11y ago
What does "performance orientated" mean?
- simple10 11y agoI think performance is referring to apps that load fast (server side rendering + AppCache + hot module loading) and using service workers for keeping the main thread running fast.
- wanda 11y agoService workers or web workers?
- skulbuny 11y agosimple10 said service works and the repo that we're all discussing mention only service workers. I think it'd be safe to assume we're all talking about service workers.
- mxstbr 11y agoActually, there's no server side rendering in this boilerplate yet. It wouldn't be hard to integrate, I didn't want to alienate the front-end devs who are front-end only and don't want to take care of server stuff. Might have to revisit that again though...
- mxstbr 11y agoI use FontFaceObserver (lazy web font loading), minify everything, keep the HTTP requests to a minimum (I'll have to look at that though, now that HTTP/2 is up and coming...), use AppCache and ServiceWorker to make repeat visits almost instant,... If you have any other ideas how to make this boilerplate even more performance orientated, hmu!
- ChrisCinelli 11y agoIsomorphic/universal Javascript will insure to have an app SEO friendly and fast rendering times on first visits.
- gildas 11y agoIs it really fast to handle rendering on server side? Why would it be faster than client side?
- untog 11y agoBecause it loads before the JS.
- gildas 11y agoLike any webpage, it is indeed loaded before the JS on client-side. But don't you need to interpret JS on server-side? Why would it be faster than interpreting the React code on client-side?
- firasd 11y agoClient-side: HTML starts loading, browser makes more http requests at various times (JS, CSS, images, etc.), React library loads, data loads, components are initialized, components are rendered. Server-side: HTML starts loading with component markup already initialized, (other stuff continues.)
- spinningarrow 11y agoI think the GP actually meant that the JavaScript has to be parsed anyway so on the server side you get a delay because the server does it while on the client side you get a delay when the browser does it, so how does this save time in total?
- firasd 11y agoThe main problem with client-side rendering is not the parsing time, the problem is the HTTP requests that have to complete before you can start parsing. Whereas parsing on the server side is done in milliseconds by any dynamic document, including this HN page.