Slint Matures to 1.0
slint-ui.com
Slint Matures to 1.0
1–10 of 12 posts
Re: Slint Matures to 1.0
#2Awesome seeing fundamental Rust crates maturing into 1.0. I hope this pushes Rust to gain even more traction in embedded systems.
Re: Slint Matures to 1.0
#3I’m ignorant to what this is compared to Material UI.
Re: Slint Matures to 1.0
#4Seems 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.
Re: Slint Matures to 1.0
#5I’m ignorant to what this is compared to Material UI.
Material 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
Re: Slint Matures to 1.0
#6Seems 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.
One can write slow software in any language, specially easy for those that missed algorithms and data structures lectures.
Re: Slint Matures to 1.0
#7Seems 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.
One can write slow software in any language, specially easy for those that missed algorithms and data structures lectures.
Yes, but the above comment is more about cache misses and constant boxing. That was a different lecture
Re: Slint Matures to 1.0
#8Earlier quoted context omitted.
One can write slow software in any language, specially easy for those that missed algorithms and data structures lectures.
Yes, but the above comment is more about cache misses and constant boxing. That was a different lecture
Nope, that would be algorithms and data structures II.
Re: Slint Matures to 1.0
#9Seems 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.
One can write slow software in any language, specially easy for those that missed algorithms and data structures lectures.
I 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.
Re: Slint Matures to 1.0
#10Earlier quoted context omitted.
One can write slow software in any language, specially easy for those that missed algorithms and data structures lectures.
I 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 someo…
Knowing which languages are better for what class of algorithms and data structures is part of it.
The math theory behind algorithms and data structures is only half of the story, the other half is understading how they map to each programming language specifically, and how to use profilers, not guessing and hunches.