3 ms·
This post is talking mostly about CSS and it shows a document object model tree. JavaScript is also used, given that he mentions React. Among these options, it
by iso8859-1 5y ago
This post is talking mostly about CSS and it shows a document object model tree. JavaScript is also used, given that he mentions React.
Among these options, it seems that Rust is most similar to JavaScript. But this whole article would be the same if React was written with Rust instead.
So what is the broken part of GUI development, and why is Rust positioned to fix it? As I see it, not much would change if we used Rust instead of JavaScript, except that it could be harder to diagnose when ReactInRust is being used.
- virchau13 5y agoThe broken part is that it is worth it to use an inefficient rendering method (lots of JS generated by React + an interpreter and GC + a render tree (React VDOM) + an overcomplicated element tree (DOM) + a rendering system) instead of an efficient rendering system (if React-in-Rust existed, it would be native executables manipulating an in memory tree for a renderer, removing at least two layers of complications). And this seems to be simply because the React+JS model works so well for DX compared to the rest that it allows for way faster feature implementation.
- jkelleyrtp 5y agoI’ve been working on this :) https://dioxuslabs.com/ https://dioxuslabs.com/
- eyelidlessness 5y agoAmusingly, SwiftUI seems much better suited to this use case than any other lower level language, while Elm and Clojure are much more obvious contenders. In any case, the space is crowded with DSLs and the expression-based DSLs are the ones that generally keep gaining traction.