git was created because a proprietary VCS was being a dick

Isn’t #2 the only option?

Websites specifying color for foreground (or background) and assuming browsers will use whatever color they’re expecting for the other has always existed, and still exists

If you’re getting fancy and specifying colors, you can’t cheap out and not specify all colors

If the browser ignores all your colors at that point, then it’s displaying as the user intended

If you only specified some of the colors, it’s a bug of the website

The even crazier part to me is some chip makers we were working with pulled out of guaranteed projects with reasonably decent revenue to chase AI instead

We had to redesign our boards and they paid us the penalties in our contract for not delivering so they could put more of their fab time towards AI

It’s a strange suggestion after very recently working closely with openSUSE to ensure Leap can use the same binaries as SLE, though

Separated over the PCIe bus with an IOMMU between it and system memory, as well as hardware switches to disable it if I’m not reachable

I haven’t found a way to remove it entirely. It’s the only option I’ve found so far, but if you know of a better designed option, I’m certainly interested

Well, a.out doesn’t make much sense these days.

Gotta move to .elf

North/south imply certain regions can’t improve and is far worse than developed/developing

If layperson words didn’t have an issue with 1st/3rd world, you wouldn’t see so many comments about it

Yup, it does change. It was attempted to mean “poor” and it’s been reappropriated since

If you’re trying to use modern language, it’s “developed” and “developing”

We went with moissanite, and everyone thinks its an insanely expensive diamond

Moissanite is sparklier than diamond, so for what people look at in rings, it ends up looking better than diamond

It looks like an alternative to LocalSend rather than Syncthing

You have to enable developer mode and install with --bypass-low-target-sdk-block now.

Dunno if they’ll remove that eventually

For the Steam Folders, you can use Flatseal to declare other folders any Flatpak you install is allowed to access

Google is certainly planning on it being viable.

They’ve been merging RISC-V support in Android and have documented the minimum extensions over the base ISA that must be implemented for Android certification

Yeah, that’s bizarre. I’d never have guessed /home was created by tmpfiles

Thanks! That sounds like exactly what I’d want to run mpd. I’ll check it out

For virtualization, I’m all good since I went with uBlue instead of Silverblue for now - the developer images come with lxc/lxd/qemu/libvirt :)

To expand - DirectX is a proprietary Windows solution. Any time you pick it on Linux, it will run through a translation layer

OpenGL/Vulkan are cross-platform

OpenGL is to DirectX 11 as Vulkan is to DirectX 12

Microsoft kept the same branding, but also followed in Vulkans/Metals footsteps of using lower level calls to the hardware. This makes the graphics drivers simpler, and can be way more performant because the CPU doesn’t have to do as much

Hey! Thanks!

I’ve installed Aurora to my new drive based off the comments here so far, and it’s been pretty smooth bringing my configs over :)

Immutable is new to me, so I’m wondering how you manage host daemons and cli applications, such as mpd for music and password-store for password management

Is the best practice to keep one Fedora <current release> distrobox with them?

Also, are there any issues with upgrading a distrobox to a new major release over time?

So far my mindset has been make sure I don’t layer anything, but maybe some things like mpd do make sense to layer?

I also see brew as another option. Perhaps that’s the preferred way for those types of tools? However, it seems like the system upgrade script updates distrobox and not brew?

Sorry for the rambling question - just trying to understand best practices with an immutable distro 😅

When I check out the ISO for microOS, it lists microOS Kalpa as “alpha”

Is it ready to be used as a primary install?

The developer image, dx, includes rocm-hip and rocm-opencl:

https://github.com/ublue-os/bluefin/blob/main/packages.json

The packages under “dx” are the main reason I’m considering it over stock Fedora

How does bluefin fit in the dependency chain here - is this just the repository that builds official uBlue images?

Part of my confusion is trying to understand how these projects are related to each other

Edit - oh, I guess bluefin is the Gnome variant