Ok, now I kind of want this. I only have my PC connected to the TV, so I only need the power button, volume controls, settings and the D-Pad. A specialized cover would make hitting the right buttons in the dark much easier and also remove the ads disguised as buttons.

And you can even go a step further and configure it so all the ISOs go into a subdirectory. Then you can still use the USB for other stuff without it becoming a mess. Right now I have the following structure:

├ apps // Lots of portable apps, using the PortableApps system
├ data // For copying files between devices
├ images // ISOs go here, separated into Linux, Windows and Utilities
├ installs // For apps that need to be installed
├ secure // Encrypted Veracrypt store
└ ventoy // Ventoy config

All that on a tiny USB on my keychain and super useful when you’re the IT person for the family.

Now I’m thinking about a proper “programming language” for cooking recipes.

Just imagine the possibilities: Automated checking for for allergies and such, easy substitution of ingredients as well as portion calculations, being able to fork recipes and change them to your liking, and later diff the recipes.

(like do I seriously need No Man’s Sky installed all the time for the once every three months that I play it?)

That sound’s like the data is in semi-regular use at least. For me it’s more like “Do I seriously need the sequel installed for that other game I haven’t even started yet, but am definitely going to start any day now, after years of having it installed?”.

Cries in nvme1n1p6, which is my current OS partition.

The topic is bloatware, not games.

The original post includes two gaming examples, so it’s actually about both, which is a bit unfortunate, because as you’ve said, they’re two very different things.

I think the examples given are just poorly chosen. When it comes to regular applications and DRM, then yes, that’s ridiculous.

On the other hand, when it comes to gaming, then yes, give me all the raytracing and visible pores on NPCs. Most modern games also scale down well enough that it’s not a problem to have those features.

Looking into the metadata of the included PDF version reveals that it’s from 2004, so even a bit older than that.

All they had to do was to allow me to move the taskbar to the side and I’m only partially joking.

Don’t worry. There’s still plenty of ESP32 waiting to be flashed with ESPHome and placed into their own little enclosure out there.

Source: Me, who’s got a Bluetooth Proxy for my adjustable desk and some small LED strips running, with a soil moisture sensor planned as my next quick project.

This particular issue was caused by a breaking change in Plasma 6 and bad handling in a specific global theme.

The general security concerns that were being brought to light however apply to all versions.

Huh, when I first checked out Hyprland under 535 drivers, it was barely working under Wayland, whereas Gnome and KDE worked at least decently well. Might have to check it out again now that some time has passed, although I still hope that the next beta driver will finally fix most things.

I wish that were the case. It’s obviously not a thing at all in Gnome (yet), but from my experience and what others are reporting, VRR is also pretty broken on KDE Wayland for NVIDIA GPUs. It works fine 90% of the time, but at certain loads it starts rendering frames out of order. As far as I can gather this won’t change until there’s proper esync support across the whole render chain for NVIDIA, starting with the drivers.

I think the first one can be circumvented by just using a DP->HDMI adapter. But yeah, those other points are why I’m a bit hesitant about swapping to AMD myself.

Or you might want to use G-Sync or other forms of VRR on a multimonitor setup, which you can’t do under X11 and is broken on Wayland.

Not exactly the same thing, but the xone (XBox One controller driver for Linux) project disabled Issues on Github and uses a Discord server instead. Which is stupid as heck, because I’m not going to join a Discord server just to check if someone has already encountered the same issue as me.

The naming of WSL sort of makes sense because it’s actually build upon a kernel feature, which hass been mostly unused for more than a decade, called subsystems. There’s the ‘subsystem for Win32’, which is the primary one that all Windows applications use, and then there were also the ‘subsystem for POSIX’ as well as the 'subsystem for ‘OS/X’. WSL was simply a reboot of that technology.

The funny part is that this turned out to be too complex so WSL 2 ditched all that and simply uses a VM running the actual kernel in the background, so the name isn’t even accurate anymore.

Not sure how standard this is, but on Pixel phones the default is no auto rotation, but when the phone detects rotation it will display a tiny rotate button in the corner of the screen for just a few seconds. Best of both worlds IMO.

The way WSL1 worked is actually quite interesting: The NT kernel always had the capability to run multiple subsystems, with Win32 only being one of them and there were subsystems available for OS/2, POSIX and later UNIX. WSL1 was pretty much a revival of that feature. So WSL1 is indeed somewhat like Wine, but making heavy use of some features built into the kernel. So yeah, no real boot process happening.

(Also it’s kinda stupid that the ‘S’ in WSL2 still stands for ‘subsystem’, despite not using that feature anymore.)

A nice grid lined notebook and a mechanical pencil is still my favorite.

If only my default font wasn’t so bad that it causes data loss.