What’s the privilege boundary here? Not being facetious. The self-hosted DOM of my dreams would follow the principle “functions that the user can compatibly polyfill in JS are in JS, while others remain in Rust”.
Well, let’s not do that then :) You can always replace that stuff with JS containers. This may have some kind of ergonomic cost, but I’m inclined to suggest that DOMRefCell and Traceable (in addition to memory unsafety!) are much worse ergonomic costs.
-
-
Josephine would let us have our cake and eat it. I would much rather avoid JS collections.
-
Doesn’t Josephine have an awkward cursor API you have to deal with?
- 4 more replies
New conversation -
-
-
I wonder if a proc macro could reasonably translate rust-style structs & enums into JS objects & collections without too much ergonomic overhead. That'd be pretty neat!
-
a.k.a. “Objective-C for the JS object model” :)
- 1 more reply
New conversation -
-
-
Yeah definitely
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.