1: 2017 is such an exciting time for the web, and I'm loving how much it's fitting in with the Glimmer work. - WASM is finally here, and Glimmer is teed up to use it directly pretty soon. - Firefox shipped Rust, which is also going to make front-end WASM awesome
-
Show this thread
-
2: - (specifically, Rust to WASM is going to be a thing and open up very low-level front-end code to way more people) - Glimmer's gonna be using Rust to WASM if everything continues to go well. - Fine-grained parallelism with SharedArrayBuffer is here,
7 replies 23 retweets 80 likesShow this thread -
3: (on top of the existing transferrables), and DOMChangeList is going to make it possible to batch up a whole bunch of DOM work in a worker and apply it all at once. Glimmer is going to have a polyfill for this that uses Rust-to-WASM pretty soon.
2 replies 13 retweets 52 likesShow this thread -
Replying to @wycats
This seems like the biggest deal of the list. That should be a boon to every JS framework, right? Is there anything about its design that would make it hard for P/React to capitalize on it? cc
@_developit1 reply 0 retweets 1 like -
Replying to @AdamRackis @_developit
Nope. The only interesting thing is that you need to reify DOM nodes from tokens after the whole tree is inserted, but that shouldn't be too hard for any framework with an equiv of componentDidMount.
2 replies 0 retweets 1 like
The only thing about it is getting it over the finish line. I should have a wasm version of it pretty soon after I have a good Rust->WASM workflow, which people can mess around with.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.