It is absolue in safe Rust, aka 99% of Rust code.
It is absolue in safe Rust, aka 99% of Rust code.
They dix not build the compositor from scratch, they built it on top of smithay, a library similar to wlroots but written in Rust.
I don’t know if you’ve actually tried to use GTK or QT, but it’s insanely painful. There is a reason almost all apps are written in Electron. Native GUI toolkits suck. If they had used GTK they would have still had an outdated and hard to maintain toolkit, and to deal with Gnome politics. Using GTK was actually the initial idea.
If we want Linux Desktop to succeed, at some point we have to build tools that people want to use. I’m glad they’re doing it.
For dôme reason it’s broken for me. I had to open it in nightly for reader mode to work.
Unreadable on mobile…
But they don’t support the same API. This is completely off topic.
The backend is not
They don’t have a client but both allow you to just download the game and run it from a .sh
that installs it in the local folder. That’s enough for me but I agree it may not be for everyone.
Itch and GOG have decent linux support
Zig is a very new and immature language. It won’t be kernel-ready for at l’East another 10 years.
That’s pretty suggestive. Rust syntax is pretty good. Postfix
try
is just better for example.Zig also uses special syntax for things like error and nullability instead of having them just be enums, making the language more complex and less flexible for no benefit.
Syntax is also not everything. Rust has extremely good error messages. Going through Zig’s learning documentation, half the error messages are unreadable because I have to scroll to see the actual error and data because it’s on the same line as the absolute path as the file were the error comes from
That’s a library design question, not a language question. Rust for Linux uses its own data collections that don’t perform hidden memory allocations instead of the ones from the standard library.
I don’t know, Rust is one of the most readablelangueage for me.
Is it still the case once you have a very large project and make use of comptime?
Not true. Because it doesn’t have the guardrails that rust has, you must build a mental model of where the guardrails should be so you don’t make mistakes. Arguably this is something that C maintainers already know how to do, but it’s also not something they do flawlessly from just looking at the bugs that regularly need to be fixed.
Being able to write code faster does not equate being able to write correct code faster.
Yes, because it’s basically C with some syntax sugar. Rust is a Generational change.