> Unlike common object-oriented GUI frameworks, Ribir widgets do not need to inherit a base class or hold a base object. It is a pure composition model
I'm really not sure how this "composition" is any different to the usual inheritance you see in frameworks like QML *in practice*.
I might still got ptsd from a job where literally all of the rust codebase was written as macros. Since then I avoid them at all costs.
I find the route, that gleam took, way more elegant with squirrel (sqlx-ish) and lustre (elm-like) being examples of what we could have instead. Avoiding language mixing is so important for proper/clean lsp-support - yet macros are a different language as i see it.
As for the rest of this: i also don't see how it's any different from iced, egui etc. but maybe I didn't take the time to check the details...
This may not be what you're after, but note that egui and Slint have accessibility support (at differing levels of completeness), e.g. for blind people using screen readers, while Ribir and GPUI do not.
reply