These 2 things are unrelated. The react-compiler gives us automatic memoization. This allows us to write idiomatic react code without worrying about performance as much. Basically, we don't need to use hooks like useMemo and useCallback anymore. The "Next.js rust based compiler" is an alternative to webpack. At least, I assume you are talking about turbopack. More on reddit.com

Hello ! This is not mentioned in the documentation, can we expect this feature to be available in page router ? More on github.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

Easily tiptap. Docs are great, great tutorials online, highly customizable. Built a couple of things with it, would definitely recommend. More on reddit.com