HN user
The main reasons (IMHO) to have SSR are:
* SEO capabilities * Faster response for first page load
And for both of those, a CDN is useful, if not essential - you're missing out on a lot of performance boost if you don't.
Other reasons to have SSR include things such as unfurling, where a CDN isn't essential, but still nice to have.
I know right, 2 spaces for indentation!!!
1989 - 2007: notes.txt, 2007 - the future: notes.md
I have a non-mac keyboard, I had to unplug it before the latest update would get past the boot screen, that's never been an issue with the past updates, maybe that's what they experienced?
Anyone got a link to their status page? My Google-fu is failing to find it...
I think there are some interesting points here, though many (including the author) seem to forget: React is a UI library, not a framework. This means it is up to the user to decide and implement everything else, such as:
* Code splitting * Loading of the code (at appropriate times, eg: ) * Any other optimisations
I think the author simply failed to do this well and then blamed the library for their own shortcomings, and moved on to the 'next shiny thing'.
There are plenty of patterns you can use to make your React app responsive, and many tools to help you achieve that, it's just a matter of being able to implement those tools effectively.
Whilst I agree, Mithril is also a very different beast - it includes a routing system, and full MVC - React is just a view component library.
Yeah I got it running - not encouraging results - image sizes grew by about 10%.