Wasn’t it supposedly affecting ALL Gnu/Linux PLUS others?

That’s so weird that my GNU/Linux isn’t affected by this vulnerability…

Next time that margarine is going to scream “wolf”, I will take it with a grain of salt…

Source: https://nitter.poast.org/evilsocket/status/1838169889330135132

I don’t know if having an unavailable wife for the next 10 years to let her compile is a “happy life” thought.

Evolution happens by iteration. Every iteration hopes to be a little bit better by bringing something a little bit differently.

F1 cars are a good example of that. Yet, nobody is going to say F1 from the 90’s could compete with today’s version.

And, anyway, time well spent for someone is always a waste of time for someone else.

BTW, I want to thank all the Void Linux contributors for that excellent distribution. It has been a while since I changed my main distro.

I was using Debian for 15 years; but sadly it didn’t evolved much and something new appeared…

You might want to check if your drivers are in the nonfree repo for your speakers/ACPI…

My laptop need those for, let me check… the sound and the ACPI :D

That’s Void Linux, exactly how I would describe Void…

Well, I believe it takes more than a day or 2 to really test a driver.

“Testing team” or not, by seeing the releases of, for example nvidia, I don’t take their “testing” seriously…

No wonder so many people are complaining about the stability of arch…BTW… ;)

Source: Nvidia “verified” drivers

I am not here to convince you, but if you happen to look at Linux again, check out Void.

Arch, but it’s tested (no dis to arch here… Just a fact).

I don’t know much about BSD, but apparently it’s an hybrid of Linux and BSD. The Void creator is an NetBSD dev.

Not the best source, but here: https://itsfoss.com/void-linux/

We will miss the days Linus was maintaining the Kernel… Who is going to write those poetic emails we all love?

it’s more “it forces you to make it burrow checker friendly”.

A burrow checker is not the only mechanism to write safe code. All the mess of Rust is all because this is the strategy they adopted.

And this strategy, like everything in this world, has trade offs. It just happens that there are a lot, like, - a lot -, of trade offs, and those are insufferable when it comes to Rust…

Zig is “c”, but modern and safe.

The big selling points compared to Rust are:

• A better syntax
• No hidden control flow
• No hidden memory allocation
• Really great interop with C (it’s almost as if you just include the C code as you would in a C code base…)
• Fast compile time
• it’s more readable
• it’s simpler to learn

The syntax is really close to the C language; any C programmer can pick up Zig really fast.

IMO Zig is a far better choice to go in the kernel than Rust.

Linux has tried to include CPP in it, and it failed.

So imagine if trying to fit in a C-like cousin failed, how far they are to fit an alien language like Rust…

For more information: https://ziglang.org/learn/why_zig_rust_d_cpp/

And probably sometime the guy who executed the command…

As a Linux only user, I totally agree with your message.

People who downvote you aren’t of good faith, are delusional or just dumb.

Linux is better in every single category except ease of use for non-technical users and gaming.

Let’s stop with this bandwagon of MS bad, Linux good; Linux is good enough for us to not lie and speak the truth…

I am waiting for Ghostty…

It’s made in Zig with a focus on performance while giving a good set of features.

Look it up!

What?

Rust doesn’t solve all security issues in codebase?

People should take note of that; I surely did…

Void.

It all started by curiosity: “let’s try this no-where distros for the lulz”

Then it ended up to be the distro I am using everywhere.

It’s stable and quite on the “bleeding edge” in term of software versions…

And damn it’s fast son!

It’s made in rust, therefore it must be safe!

Comptime replaces macros/reflection.

It’s basically Zig code that runs at compile time in your code…

No other “weird” language to learn; it’s zig all the way. What you would have written in macro is written in zig comptime.

Even the build system is zig…

Same for generics, it’s comptime…

As I mentioned, a couple of tasks loosely related. The patch you are mentioning isn’t complete nor address the real problem.

It is an ugly hack at best.

Refrain from your urge to defend rust at all costs. You are sliding more and more toward the specifics of a project than the fact I stated about rust in general.

If you still not get my initial point I’ve made, read this.

That’s a long read explaining what I meant. My point was about Rust, not Zed or the developers of Zed in particular.

And for the Zed editor, I wish them the best luck, it seems like a great project that people enjoy.

Please feel free to comment and share your thoughts on the article above, my dear favorite nutritious veggie.

Wtf are you talking about? Redis is in C…

There are no patch, the issue has been closed as in rejected.

There are a few tasks that are open that are loosely related, but let’s not mix things up.

Moreover, I will take the words of the maintainers over a random potato on a forum.

No offense…