http://expo.io/

More on reddit.com

For anyone reading this I found this youtube video and I stronly suggest you to watch it! TLDR: "it's good enough" and in my opinion will do the job better than me. But it is not magic though and there are a lot of cases where manual optimization is probably needed. https://www.youtube.com/watch?v=T-rHmWSZajc More on reddit.com

Wtf?

More on reddit.com

One ever present debate in the React community had been whether you should `useMemo`/`useCallback` all non-primitive props or not. I've often taken the position that you should in real world teams because it's too much work to determine exactly when to otherwise , whereas others argue that it's too much runtime overhead (and noise) and not worth it. u/acemarke has a good summary of the arguments . All that to say, I was curious if this compiler is essentially the React team conceding that you _should_ memoize everything. The answer is pretty interesting - the compiler actually memoizes things in a more efficient way than `useMemo` can . So it's almost the best of all worlds: improved rendering performance from memoization, cheaper memoization cost, and none of the noise of `useMemo`s sprinkled everywhere. I think we'll have to wait a bit longer to see if this works out in practice, and I'm not crazy about having to add another layer of transpilation, but if it works well this will be a pretty big win for React projects in general I think. More on reddit.com