5 ms·
It would be really interesting to one day have React be a polyfill for an in-browser async DOM renderer. Is that in (very, very, long-term) consideration?
by yazaddaruvala 9y ago
It would be really interesting to one day have React be a polyfill for an in-browser async DOM renderer.
Is that in (very, very, long-term) consideration?
- danabramov 9y agoI think my talk paints a relatively convincing picture why DOM nodes aren’t a sufficient primitive if you care about the features I described, as you’d need something like React to orchestrate those updates.
- crudbug 9y agoHello Dan, Great talk ! My thinking behind the top statement was with a native implementation of react-core, the react-native story becomes more compelling with JSX(ish) UI templates / CSS Styles and multi language business logic support. Once you have this, the browser becomes another target. I see Flexbox implementation is already native with Yoga [0]. [0] https://yogalayout.com/ https://yogalayout.com/
- yazaddaruvala 9y agoOh sorry, I didn't do a good job explaining myself. Currently: Application(JS) + React(JS) | Browser(C/C++/Rust) Possible Future: Application(JS) + React(Polyfill - JS) | React(C/C++/Rust) + Browser(C/C++/Rust) Something akin to the Browser building a "higher level" React-like API/scheduler for the DOM.