a personal life update: I'm closing the React Native chapter of my career.
I'm very grateful for these 6+ years; I wrote a bit about it all here 👉 kelset.dev/blog/closing-t…
Kind of a big news: I recently joined @Microsoft!
I have just written that and I still can't believe it 🤯
I've been feeling ALL THE EMOTIONS and I'm still learning a ton of new things everyday - but as it settles... I feel I'm in the right place.
Long road ahead but I'm 🔥
Allright folks, it took a lot of time and effort but we're out: github.com/facebook/react…#reactnative 0.65 is now ready for use, I hope you'll enjoy the improvements that it brings! And I hope that the upgrade experience will be good - the upgrade helper diff looks promising 🤞
As of yesterday, thanks to the Meta team working on it, React Strict DOM is open source on GitHub 🎉
At MSFT have been in the loop with them on this since last year, and now that it's out I wanted to spend a sec on what is likely the next big thing for React as whole 🧵👇
...what if upgrading a #reactnative ⚛️ app from 71 to 72 took less than 2 minutes?
what if the majority of those 2 minutes was actually spent in re-running the app in both iOS and Android to verify that it all work?
Check this out 👀
(the video is NOT sped up)
btw @kenwheeler on stage googling the useCallback documentation to fix an issue is the most advanced thing.
We all do it, and we shouldn't feel that is "cheating".
(if you need further reassurance, check out @type__error's blogpost about it!)
#reactAdvanced
One last win to share in closing this 2023, yet again about #reactnative and in particular about some of the invisible #opensource work that you folks most likely didn't notice 🥷
If you go on the React Native repo right now, you'll see that the number of open issue < 1000:
All right folks, this was a loooong one to prep up but
HERE
IT
IS
the 1st part of my 4 blog posts series about the new #reactnative architecture.
For long time the only material about it was super high level, so I aimed for a "beginner-friendly" approach:
