A cool thing I'm noticing with Gloo, is that we can enforce so much more invariants around Web APIs compared to Choo. To name a few: - compile-time enforcement of transactions for IndexedDB - duplex byte stream interface for WebSockets - FnOnce for events that fire once
-
Show this thread
-
Because Gloo is essentially laying down a foundation for future Rust - Browser interactions, it seems likely it'll be perceived by most people as "Rust's DOM bindings". And if my instincts are right here, the sheer quality of it is likely not going to go unnoticed.
1 reply 0 retweets 3 likesShow this thread -
I think this has the potential to change the narrative around WASM also. For most people on the web it seems to range from "sounds interesting" to "useful in specific cases". But Gloo might just change that to: "WASM allows us to redefine what web development should feel like".
1 reply 0 retweets 4 likesShow this thread -
All of this is coming from a very practical POV btw. I've spent years polishing JS bindings to every web API under the sun. And they are great to use! But now I'm seeing what Gloo is doing. And the UX is *so far* ahead of what we were able to do. It feels significant.
1 reply 0 retweets 10 likesShow this thread -
rustwasm/gloo
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.