Re:Towards Principled Reactive UI
by ComputerGuru on Sunday September 27, 2020 @03:17AM
(#24604868)
Rust solves the closure problem with its borrow checker, closures are heavily used through the rust ecosystem. ( I didn’t downvote)
C++ is a systems language, yet Qt seems to be quite a successful GUI toolkit.
Qt has issues with lifetimes of objects. It's easy to shoot yourself in the foot by accessing objects that have already been destroyed. The borrow checker can solve that, but still shows that C++ was not really the best choice as a language for building UIs.
I also think that the success of the combination of Qt/C++ is mostly a result of the evolution of programming environments. C++ was massively popular, so that could explain it.
You’re being downvoted but I agree with your opinion.
This blogpost doesn’t show any UIs built with this rust paradigm, and the github homepage only displays a few screenshots of a calculator app.
Technically, it appears interesting. Practically, it seems very far off from the tools I use to build usable (or hopefully aesthetically pleasing) UIs.
Re:Towards Principled Reactive UI
by chrismorgan on Sunday September 27, 2020 @05:35AM
(#24605405)
That’s… kinda the point of research work. No one claimed it was ready to replace the tools you use in production.
Of course, you can still write your low level bitblt functions in Rust if you need to (though these functions are probably best left to a GPU). But an entire application and its UI, then you're probably pushing it too far.