Not my blog, but you might find this useful.
Cheatsheet: https://devhints.io/gnupg
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.
C wasn’t my first language, but I learnt the most whilst learning C…
People are talking about footguns and what not security related issues. I agree it’s easy to write bad C code, but if you want to learn what’s going on, learn C.
Today I know a dozen of programming languages and C has always been in a special place in my heart. I am using Zig for my personal projects at the moment. It’s similar to C, without the pitfalls, and my C knowledge still helped me to learn that language.
Learning C is a service you are doing to yourself for the rest of your life.
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…
I think you’re making a lot of misinterpretation; but that’s up to you…
But, just so that I can understand correctly… When you’re saying: “if I need something more […] I click terminal tab”
That “terminal tab” of yours, it’s a CLI isn’t it?
I always love watching people falling for Clown-Bob’s advises…
Let’s go, let’s eat shit on toasts! It’s just a matter of how thin you can spread it to hide the taste…
My personal experience is most people who are using git with a GUI are the same people who are asking my help to git-fu their git-problems…
Most GUIs only offer a subset of the git functionalities and hide what’s really going on by obscuring gitshell with “their workflow”.
In all cases, use what you like; some people like the shell. Cheatsheets are normally only for learning purposes and usually don’t stick for long, it’s not an end game thing…
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?
The new technology is: show a message saying “Whoaa! You have busted your limit!” on every search.
I didn’t do a search for 6 months, but whhooaaa! Calm down with your searches!
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:
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/
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…