teolan

Voting by itself doesn't do shit. Organizing and convincing people to vote based on an issue does.

Voting isn't going to do shit.

Get involved. Protest. Refuse to work for terrible companies. Convince the people around you to protest and vote.

I'm suggesting building a Rust library and exposing a C ABI. That's what rsvg does for example.

You're aware that Rust gives you access to the full C ABI?

What language are you going to use instead that has a better ABI story? Swift? Or maybe a dynamic language like Python?

He says he has had permission. Given that it's a mostly 1 person project it's possibly true.

Like sudo that has had zero days lurking for 10 years?

I'm not advocating for reimplementing stuff for no good reason though.

And there are apps that make it very very easy and fun. Check out street complete.

You can contribute them!

There's a pretty barebones editor in Organic Maps, but you can also check out Street Complete and Every door (more advanced and less user friendly, though insanely efficient)

Zig is a very new and immature language. It won't be kernel-ready for at l'East another 10 years.

a better syntax

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

No hidden memory allocation

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.

it's more readable

I don't know, Rust is one of the most readablelangueage for me.

Fast compile time

Is it still the case once you have a very large project and make use of comptime?

it's simpler to learn

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.

Really great interop with C

Yes, because it's basically C with some syntax sugar. Rust is a Generational change.

It is absolue in safe Rust, aka 99% of Rust code.

Norway

That's not going to happen within the lifetime of the batteries of the trains though.