The solutions to both of these are based on the new asynchronous Fiber reconciler. In short, what Dan presented through fantastic demos was basically how React is tackling two things, CPU-bound performance (slow devices) and IO-bound performance (slow network). Also, this post is long and kind of technical, so grab a coffee before venturing on. (Oh, and while you are in video mode, you might wanna check out the latest talk I did at Stockholm ReactJS Meetup about the difference between initial state server rendering and full state server rendering and how to solve some of the challenges in the latter case.)ĭan’s talk is the perfect background for this blogpost which I have been meaning to write for some time now, so you really should watch it before reading this. If you are at all interested in React, you should really go watch it right now, I’ll wait. At the Swedish public service television company we are heavily invested in server rendering as a means to deliver our digital experiences to as many citizens as possible, so I thought I’d take some time to share a few thoughts on this, but first, some background.Ī few days ago Dan Abramov delivered another one of his stunning talks, this time the topic was the future of React. The recently revealed React suspense functionality has the potential to solve a lot of the current pain points in server rendering.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |