| ▲ | ogoffart a day ago | |
> Either it's a rust library or it's not. It is one. Your app is a Rust program that depends on a crate. The UI compiles to Rust code, and we also have the `slint!` proc macro. > there's always some edge case logic that needs a full programming language Right, and that language is Rust. The DSL only describes the GUI. You operate it from Rust. > Why was using js like qt quick not good enough? QML was the inspiration. I worked on Qt and wrote QML bindings for Rust before (qmetaobject-rs). Slint is a new take on it, compiled ahead of time, no GC, strongly typed. | ||
| ▲ | noodletheworld a day ago | parent [-] | |
> The UI compiles to Rust Right, so not rust. Languages that compile to c are not c. Languages that compile to rust are not rust. > QML was the inspiration Yes, except you invented a new programming (1) language unnecessarily. Whatever. We'll have to agree to disagree. If the programming language you write is not rust it is not a rust ui library. Slint requires you to write your UI in slint. I havent used it much, but Ive used it enough to know that this: > The DSL only describes the GUI Is about as disingenuous as you can get. Thats like saying that javascript only describes the GUI of a website, a backend rust website is really just a rust application. Really you're building in rust. React is really a rust UI library at heart. <—- obviously BS. (1) - https://docs.slint.dev/latest/docs/slint/guide/language/conc... | ||