5 ms·
Slint Matures to 1.0
- rendaw 4y agoWhat's required to package a program up? If the UI library is native all you need is the Rust binary, but since this also works with C++ and JS is it dynamically linked to some runtime files that need to be packaged as well? The tutorials don't seem to cover this, and it's the number two thing I look for in a UI toolkit (first being language). I chose JavaFX for a project because the cross platform packaging was automatic, despite numerous other limitations. I've had enough dealing with packaging GTK and Qt in the past...
- cstrahan 3y agoThey have separate backends for the languages, which is just like any other library for the respective language. E.g. in Rust, the Slint libraries are linked into the executable just like any other Cargo dependency — no need for separate DLLs/shared libraries to be installed on the system.
- nhatcher 4y agoAwesome seeing fundamental Rust crates maturing into 1.0. I hope this pushes Rust to gain even more traction in embedded systems.
- LivingGlitcher 4y agoI’m ignorant to what this is compared to Material UI.
- 3836293648 4y agoMaterial is a design style made by google. Material UI is a react library that implements this style. This is a from the ground up ui library primarily for native applications written in rust, though it also as a web backend
- return_to_monke 4y agoSeems like Slint is trying to be a Flutter but for rust - which is a very nice thing. Dart has a lot of bad coding concentions taken from Java (eg classes everywhere) which make it really easy to write slow software.
- pjmlp 4y agoOne can write slow software in any language, specially easy for those that missed algorithms and data structures lectures.
- 3836293648 4y agoYes, but the above comment is more about cache misses and constant boxing. That was a different lecture
- pjmlp 4y agoNope, that would be algorithms and data structures II.
- pornel 4y agoI really dislike answers like this (which very predictably appear in every language vs language discussion). The "just use good algorithms" avoids the core argument about language's overhead, and changes the topic to a smug "I know algorithms, and everyone using the other language is just an uneducated noob". General-purpose languages should all have ability to use proper algorithms and data structures, so when someone mentions slowness of a language, it's not a complaint about programmers being uneducated. However, if some algorithms or data structures actually are pathologically hard in some language, that is a language design or implementation problem, not a "bad programmers are bad" problem either. Even when programs are properly optimized in the big-O sense using data structures that your professor would approve of, languages can still add overheads. Linear overheads still count, e.g. one language can sort 2x faster than the other, and that doesn't mean the other must be using bubble sort.
- 4y ago