React Fiber is an internal engine change. You can’t interface with it as a React Developer, and the upgrade went so smooth most didn’t even notice it happened.
So why should we care about it? Because it’s really freaking cool!
React before Fiber was like working at a fast paced company without git.
Imagine being in the middle of a huge feature, and your boss needs a hotfix, pronto.
With git, you don’t have to worry. Fiber is like that, but for rendering.
With Fiber, React can pause and resume work at will to get what matters on screen as quickly as possible! 🎉
In short, React Fiber is incredible.
Perhaps some of you haven’t found a reason to try and understand it. It could be because it’s abstracted away, or it’s not clear where to even start.
Understanding Fiber has large benefits, though. It’s a piece in the asynchronous rendering puzzle. It’s only a matter of time before other frameworks start heading in that direction.
Let me be your guide. Feel free to skip this next section if you don’t need context about how the system surrounding Fiber works! 💪