You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
🎯
Focusing
Ashutosh Singh
gladiatorAsh
🎯
Focusing
Experienced full stack engineer with skills in C#, JS, Node.js,React, jQuery and SQL.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Demo: Coordinating async React with non-React views
Demo: Coordinating async React with non-React views
tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.
A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.
But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.
FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.
Optimizing your react components via redux....shouldComponentUpdate for free and more...
The Beginning
Yes...it's true...redux is smart....smarter than you even know. It really does want to help you. It strives to
be sane and easy to reason about. With that being said, redux gives you optimizations for free that you probably
were completely unaware of.
connect()
connect is the most important thing in redux land IMO. This is where you tie the not between redux and your underlying
components. You usually take state and propogate it down your component hiearchy in the form of props. From there, presentational