had its own built in lock with a unique key

Is this a common thing? I’m Aussie so I have no idea about guns.

Hot take: If you don’t like ads, then don’t use services/sites that are funded by ads?

I like using Sriracha, or peri-peri sauce from Nando’s or Trader Joe’s.

Very popular in the Netherlands.

the scroll wheel can tilt to scroll sideways

I use these for switching tabs in browsers/IDEs by remapping them to Ctrl+Tab and Ctrl+Shift+Tab using Input Remapper

I’m just glad that KDE now has an option to disable pasting using the middle mouse button (mousewheel click). Only available on Wayland though - AFAIK this behaviour is deeply rooted in X11 and it’s not easy to disable it.

Your data really isn’t worth that much.

Also, it’s a common misconception that large tech companies like Google and Meta sell your data. They don’t. The data is what makes the company valuable - they’re not going to give away their competitive advantage. Instead, advertisers can target people based on the data. The advertisers never actually see the data nor exactly who their ads are reaching (it’s just aggregate anonymized data).

On Google and Facebook, even individuals can use the same tools that large advertisers use to list their ads, and see exactly what they see.

deleted by creator

then complain about them later.

I don’t see where they’re complaining? They don’t seem to be asking anything of the C devs other than help with API definitions.

Sounds like the equivalent of Alt+SysRq+B.

In this case, the issue is really the C kernel devs, not the Rust devs. Some are not open to new ideas at all. Take a look at the conference video he linked to for example: https://youtu.be/WiPp9YEBV0Q?t=1529. He clearly states that he’s not trying to make the C devs learn Rust.

I took down the home page of one of the top 5 websites for around 5 minutes.

There were two existing functions that were written by a different team: An encode method that took a name of something (only used internally, never shown to the user) and returned a numeric identifier for it, and a decode method that did the opposite.

Some existing code already used encode, but I had to use decode in my new code. Added the code, rolled it out to 80% of employees, and it seemed to work fine. Next day, I rolled it out to 5% public and it still seemed okay.

Once I rolled it out to everyone, it all broke.

Turns out that while the encode function used a static map built at build-time (and was thus just an O(1) lookup at runtime), decode connected to a database that was only ever designed for internal use. The DB only had ten replicas, which was nowhere near enough to handle hundreds of thousands of concurrent users.

Luckily, it’s commonplace to use feature flags changes, which is how I could roll it out just to employees initially. The devops team were able to find stack traces of the error from the prod logs, find my code, find the commit that added it, find the name of the killswitch, and disable my code, before I even noticed that there was a problem. No code rollback needed.

That was probably 7 years ago now. Thankfully I haven’t made any mistakes as large as that one again!

Always use feature flags for major changes, especially if they’re risky!

On KDE, there’s also Kate. They used to be totally different apps, but these days, KWrite is a simplified version of Kate. They both use the same text editor component, but Kate adds more IDE-like features.

Using X forwarding would require you to install big chunks of GNOME or KDE on the server. A better approach is to mount the remote server over SFTP then use KWrite, gedit, whatever, directly on your desktop.

Why would you use a mouse in a console editor? Most of the time, if you’re using Nano, it’s because you’re not in a GUI environment.

Otherwise I feel like it’s a bit pointless to put so much work into a system that can’t be kept secure,

You just need to recompile stuff when needed :D

I think it’s designed mostly to be a learning experience rather than as a daily driver. It serves that role very well!

Kinda enjoying the process of piecing stuff

At the risk of sounding crazy… You might enjoy Linux From Scratch (LFS) and Beyond Linux From Scratch (BLFS). Maybe not as a daily driver, but it’s a great way to learn how everything works, since (as the name suggests) you build everything from scratch. No package manager, just tarballs of source code. It really helps with getting an understanding of how everything works.

BLFS even includes instructions for building Xorg and all the major desktop environments.

I had an nvme ssd that refused to play ball with it, a Samsung PM991A nvme ssd

Did other NVMe drives work? I wonder if it’s using an outdated NVMe driver… Was the kernel old?

I can’t remember examples off the top of my head, but there’s been some GUI programs I’ve wanted to install that are in Fedora’s repos but not in Debian’s. I’ll have to check my installed packages at home and see.

Debian’s packages can also be very old, even in unstable. That’s to be expected - Debian focuses on stability rather than going for the cutting edge - but it can cause issues when using it in a desktop environment (as opposed to a server environment). I’ve got a Framework 16 laptop and AMD contributed a bunch of bugfixes in the 6.9 kernel, which took a while to make it to bookworm-backports.

Debian is fantastic as a server OS and I’ve been using it for over 20 years, but on the desktop I ended up liking Fedora more.

Which C++ redistributable do I need to run this program? It’s not the newest one or the year before that. It’s not the one provided by the installer. It’s 2013 (in this case only)!

Luckily, the Linux equivalent (glibc) is mostly backwards compatible. You can still hit issues if you have a binary blob that’s been compiled against a newer version of glibc than what comes with your distro, or if it’s compiled against an extremely old version of glibc, but that’s not too common.

Why does every distro need yet another package manager

A lot of them have been around for a very long time - dpkg (then apt) since 1994, RPM (then yum then dnf) since 1997 - and there’s no one package manager that’s clearly better than the others.

APT is so nice and easy… I hope DNF is the same.

dnf is just as easy, and in my experience, Fedora’s repos are pretty comprehensive and have a lot of things that Debian’s and Ubuntu’s don’t.