While moving away from IPv4 isn’t really pressing anymore, there are still avoidable annoyances in v4 land.

Just yesterday a friend and I had a lot of fun getting our laptops to connect to a public network. Why? Because IPv4 doesn’t have many private ranges and not only did the address of their captive portal conflict with the address space of a VPN we’re both in, the address of their DNS server also conflicted with the default address space my friend’s Docker setup operated in.

Figuring that out was a riot.

I run Garuda because it’s a more convenient Arch with most relevant things preinstalled. I wanted a rolling release distro because in my experience traditional distros are stable until you have to do a version upgrade, at which point everything breaks and you’re better off just nuking the root partition and reinstalling from scratch. Rolling release distros have minor breakage all the time but don’t have those situations where you have to fix everything at the same time with a barely working emergency shell.

The AUR is kinda nice as well. It certainly beats having to manually configure/make obscure software myself.

For the desktop I use KDE. I like the traditional desktop approach and I like being able to customize my environment. Also, I disagree with just about every decision the Gnome team has made since GTK3 so sticking to Qt programs where possible suits me fine. I prefer Wayland over X11; it works perfectly fine for me and has shiny new features X11 will never have.

I also have to admit I’m happy with systemd as an init system. I do have hangups over the massive scope creep of the project but the init component is pleasant to work with.

Given that after a long spell of using almost exclusively Windows I came back to desktop Linux only after windows 11 was announced, I’m quite happy with how well everything works. Sure, it’s not without issues but neither is Windows (or macOS for that matter).

I also have Linux running on my home server but that’s just a fire-and-forget CoreNAS installation that I tell to self-update every couple months. It does what it has to with no hassle.

In addition to what Wolf told you, here’s a few little extra tidbits:

Some games have native Linux versions. If they don’t, you typically play them through Proton, a gaming-ready version of the Wine compatibility layer. Steam directly supports this through compatibility settings (Steam -> Settings -> Compatibility for default settings or Game properties -> Compatibility for per-game settings). Sometimes specific Proton versions will be better for specific games but usually you don’t need to worry about it much.

Proton is damn good. Expect performance for most games to be within ± 5% of the performance you’d get on Windows. Yes, some games run better on Proton than on native DirectX.

Valve recently decided to enable Proton by default for games that don’t have a Linux version. You can enable it yourself in the settings if it isn’t enabled yet.

You can even force games with a native Linux version to use Proton by setting it in the game’s compatibility settings. In that case Steam will download the Windows version.

Seconded, with caveats. Garuda is basically a gaming-ready Arch with a few of the rough edges filed off (and a 1337 G4M3R desktop theme preinstalled). I quite like their convenience stuff but in the end it’s still Arch.

Pros: It’s easy to set up and conveniently comes with everything you need to start gaming. It defaults to the KDE desktop, which will feel fairly familiar to Windows expats. It allows you to do whatever you want to do, in true Linux fashion. Cons: It’s still Arch-based so you will be living at the bleeding edge. A certain amount of occasional instability is to be expected. The default theme might put you off if you’re not into the whole gamer aesthetic but it’s easy to change.

I also see people recommending Bazzite and similar immutable distros and honestly, I can see the appeal. They’re harder to break and Discover (or whichever Flathub frontend you use) is very welcoming and convenient for managing your installed apps.

Pros: You’re less involved with the OS’s technical underpinnings than with an Arch-based distro. Immutables are designed to be robust. The Flatpak-centric workflow feels slicker than a traditional package manager. Cons: The design restricts your freedom to a certain degree. Flatpak has a few caveats compared to native software packages.

In the end I’d say that Garuda is great if you’re interested in learning more about how Linux works and want to be able to tinker with the system. There’s a ton of resources on technical stuff in Arch and all of them apply to Garuda as well. On the other hand, an immutable like Bazzite is great if you’Re not interested in Linux internals and just want something that works and is hard to break.

To quote that same document:

Figure 5 looks at the average temperatures for different age groups. The distributions are in sync with Figure 4 showing a mostly flat failure rate at mid-range temperatures and a modest increase at the low end of the temperature distribution. What stands out are the 3 and 4-year old drives, where the trend for higher failures with higher temperature is much more constant and also more pronounced.

That’s what I referred to. I don’t see a total age distribution for their HDDs so I have no idea if they simply didn’t have many HDDs in the three-to-four-years range, which would explain how they didn’t see a correlation in the total population. However, they do show a correlation between high temperatures and AFR for drives after more than three years of usage.

My best guess is that HDDs wear out slightly faster at temperatures above 35-40 °C so if your HDD is going to die of an age-related problem it’s going to die a bit sooner if it’s hot. (Also notice that we’re talking average temperature so the peak temperatures might have been much higher).

In a home server where the HDDs spend most of their time idling (probably even below Google’s “low” usage bracket) you probably won’t see a difference within the expected lifespan of the HDD. Still, a correlation does exist and it might be prudent to have some HDD cooling if temps exceed 40 °C regularly.

Hard drives don’t really like high temperatures for extended periods of time. Google did some research on this way back when. Failure rates start going up at an average temperature of 35 °C and become significantly higher if the HDD is operated beyond 40°C for much of its life. That’s HDD temperature, not ambient.

The same applies to low temperatures. The ideal temperature range seems to be between 20 °C and 35 °C.

Mind you, we’re talking “going from a 5% AFR to a 15% AFR for drives that saw constant heavy use in a datacenter for three years”. Your regular home server with a modest I/O load is probably going to see much less in terms of HDD wear. Still, heat amplifies that wear.

I’m not too concerned myself despite the fact that my server’s HDD temps are all somewhere between 41 and 44. At 30 °C ambient there’s not much better I can do and the HDDs spend most of their time idling anyway.

Entra isn’t Azure. Entra ID is what they renamed Azure Active Directory to. But not always; there’s also Azure Active Directory B2C (yes, that’s the fully expanded name). And various other Azure-branded things that may or may not belong together.

Microsoft are spectacularly bad at naming things.

It’s a miracle they haven’t renamed Windows 11 to “360 365” or “Live 6.5” or “Active-DOS Series X” or something.

Not really. 32-bit libraries are mostly relevant for people who want to play old games, which mostly means old Windows games. Windows software doesn’t tend to use Unix timestamps a lot.

It’s not terribly exciting but I find myself using this a lot:

#!/bin/sh

echo "$*" | sed -e "s/x/*/g" | bc -l

Just a little shorthand for bc that allows me to write “x” instead of “*” to avoid shell expansion nonsense. I put it in ~/.local/bin/= so I can e.g. just write = 17+4x5. Combined with a Quake-style terminal this is much faster than launching a calculator app. It’s a script instead of an alias so it works regardless of the shell I’m currently using.

The call to bc -l could be replaced with one to qalc -t if you know qalc to be present on the system .

There’s a reason why oldschool X-Com players kept coming back to the games despite technical issues like the Groundhog Day bug. (Thank all applicable deities for OpenXcom solving those issues, though.)

My most used features so far are vertical splitters, vertical nudging, and the new placement modes for conveyors and pipes. With an honorable mention going to conveyor wall holes, which also free up a lot of design options.

Honestly, though, just about everything in this update has been a godsend. Priority splitters are the only thing I haven’t really used yet. Even the elevators rock; being able to zoop up to 200 meters up or down in one go can make them useful even as a temporary yardstick for tall structures. (Also, I did end up needing to go 150 meters straight down to get at some resources and can confirm that elevators handle their intended purpose very well.)

Given the usual quality of BIOS/UEFI option descriptions it’s remarkably close to being sensible. I would’ve expected something like “enables limiting CPUID maximum value”.

My vent core feels retroactively unblasted by this revelation. You really can’t expect anything good from any of the major studios anymore these days.

Besides, “there are only two sexes” is rather obviously inaccurate. While intersex people aren’t terribly common, they do exist and are well-documented – as are the genetic reasons for why they’re intersex. XX men and XY women are also a thing. Genetics are inherently messy.

But acknowledging all that would mean having to admit that sex is a complex matter and can’t be handled with simple statements like “the one you were born with is the one you should have”. It’s easier to just pretend intersex people don’t exist.

Holy shit, that’s much better! Thanks; I didn’t know about that package.

Unfortunately, it follows the current Gnome design language. Gnome’s approach to UI design doesn’t click with some people, me included. I feel that while the main UI has not changed much since GIMP 2, the dialogs have become far less intuitive to use.

Yeah, the 13 feels a lot more solid. The 16 pays a certain price for its enhanced configurability. Honestly, though, a full-size touchpad module would go a long way to fixing that. The two spacers next to the keyboard look fine (if the keyboard is centered) but the touchpad spacers look less great.

I have a Framework 16. Is it as well-built, efficient, or quiet as a MacBook Pro? Nope. But if something breaks I can easily replace it, and I can upgrade it without having to throw everything away. Also, hot-swappable ports. That’s nice too.

It’s all about trade-offs in the end.

Not everyone needs to talk to everyone. But many people need to talk to many people.

Microsoft had to abandon the initial Vista project and start over because they couldn’t manage a team of 1000 developers. People working on adjacent features had to go through so many layers of management that in some cases the closest shared manager was Bill Gates. For something like getting a change in the shutdown code reflected in the shutdown dialog.

Huge teams become exponentially harder to manage efficiently.

I hadn’t heard about Copilot telling people how to activate Windows 11 without a license, though. So I’ll thank OP for that bit of levity.