Rust:

Still fighting the burrito check fil er

When Stallman was saying that smartphones would become a spying device, people were calling him crazy.

I am still thinking he’s a bit on the crazy spectrum, but that some food for thought…

How ironic your comment could be…

No one said multiboxing is botting here…

Wanna fight me “bro”? Bring your bots and I will bring mine, let’s see who get the best bots.

EvE was nice before f2p. Now it’s a botfest with 1 man army.

Imagine the amount of dependencies for a project like that… That would fix the seg fault memory issue, but only to end up with an out of HD space issue.

Don’t take it personally.

It’s how the guy who wrote the blog sounds like, it’s not toward you.

I tend to have a grain of scepticism when someone is declaring high and loud that something widely used us /just the worst/.

Also, it just happens his alternative is just: “use this instead, its made in Rust”

…

TL;DR here.

GnuPGP is bad. It’s so bad, it’s terrible. Don’t use it, it’s the worst. You know this GNU? It’s bad, terrible.

Use this one instead, it’s coded in Rust…

Lol OK… Thanks I guess…

Not my blog, but you might find this useful.

Cheatsheet: https://devhints.io/gnupg

For my part, I couldn’t care less about your windows app frustrations and your “intention to leave Windows”.

If I wanted to hear what’s happening on Windows, I would have subscribed to some Windows related channels. I didn’t.

Your post has nothing to do with Linux.

You have to change… 1- your default OS language (download all the language files, ZzZZz) 2- change the locale 3- apply the new locale to “all”, which is the login screen, current user, new created user.

Go in regional settings and adjust if needed, then reboot with a USB drive on a distro of your choice,

1- go through the installation 2- update if needed

Now you should have the desired keyboard.

The only argument I see in favour of varlink is the ease of debugging, and this should never being an argument in a technical decision.

When your stuff is running in “prod”, your " ease of debugging" is thrown away, but the system continue to suffer.

Json for IPC is a terrible idea.

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…