3 ms·
Agree with sibling comment - the JS ecosystem has a huge momentum behind it and probably isn't going away anytime soon. On the web, Wasm has currently found th
by hsheth2 5y ago
Agree with sibling comment - the JS ecosystem has a huge momentum behind it and probably isn't going away anytime soon.
On the web, Wasm has currently found the most success with compute-intensive applications, since the JS <-> Wasm bridge is still pretty expensive. There are already some Wasm-based frameworks like https://platform.uno/ https://platform.uno/ that work on the web, but things like React/React-native and Flutter have a huge head start.
- WA 5y agoReact is for connecting state to the DOM and managing the redraws. I don’t see how Wasm could ever replace React, if you want to deal with UI. It’s a different thing.
- hsheth2 5y agoIf we get to a point where interacting with browser DOM is comparably fast with Wasm, either through JS or with native APIs, then we could see Wasm replace React. That said, you're right that we probably won't see anything of that sort in the short term.
- WA 5y agoBut how? React is a library to implement and structure your architecture in a certain way. Wasm is just a language. Wouldn’t you need a React-like framework in Wasm to get the same benefits? Edit: I guess you mean you’d compile your React app to Wasm, no?
- hsheth2 5y agoYes you’re right - I somewhat conflated two different things. More clearly: once Wasm interactions with the browser are fast, a new framework + Wasm could replace React + JS.