Daniel Friesen

> However I'm still not keen on the idea that we're sacrificing the purity of the render method because we have to track keep() calls. I agree that your API...

> What I like about this idea though is that the return value of createReparent() can now easily be a component itself which makes it a mot more intuitive to...

Hello @gnoff, I posted an alternative API idea awhile ago but never got around to writing an RFC for it and I'd like to get your opinion on it. The...

@j-f1 Interesting idea, though rather than HOC I presume you mean render function. ```js let Consumer = ({context, children}) => { const data = useContext(context); return children(data); }; const KeyContext...

> I think this proposal breaks one of react's base principle: > > > `useRef` returns a mutable ref object whose `.current` property is initialized to the passed argument (`initialValue`)....

@theKashey Sure, that is an alternative I listed (no. 3). I will note though. One of the original idea for hooks was supposed to be that they could eventually be...

> I think the general thinking here is that we want to do something like this but it'd be a breaking change and only worth doing along with other breaking...

> Default export is not the right way to import from react. `React` is a namespace. You're going to have to rally for JSX to be changed then. Because the...

> I'm talking about the time when react will have esm and named exports. React's single file bundles were an intentional choice, even if React ever gets ESM it will...

> How does this proposal hold up against the latest shipped Node implementation? There seem to be some changes to the ESM handling. The general idea of the RFC seems...