jcastro

I ran chimeraOS for years and it worked fine, I switched to dogfood more than anything else. If your system is working there's no reason to mess with it.

> But I suppose there won't be optimizations for any combinations of GPU/CPU/RAM like Valve and AMD do for the Steamdeck?

I run a homegrown gaming htpc with an R5-5600, Radeon 6800XT, and then the Xbox wireless dongle and 4 Xbone controllers with Bazzite.

You'd be surprised at how much of heavy lifting is done by the kernel and mesa stacks, that's where the real work is done. Fedora does a good job pulling in kernel and mesa updates relatively quickly and the steam client handles the proton updates.

There's also great synergy between Bazzite, ChimeraOS, and Nobara, which are all gaming focused distros. Lots of code sharing and teamwork happening there, which is awesome to see. Everything is open for people to hack on.

It acts like a big steamdeck, all the performance overlays work, all the xbox controllers work ootb, fsr works, etc. - you do need to pair the controllers with each controller but that's a one time thing. I've personally completed God of War, Horizon Zero Dawn, Baldur's Gate 3 and other AAA campaigns in 4k. And then when I need to travel all my game progress is on my deck. It's a full multi device experience.

But to set expectations: VR and multiplayer games that don't opt into EAC or use kernel-level anti cheat are a no-op, as well as anything Epic makes. To me it's just like any console platform, you get lots of games, and some games you can't play. At this stage in the game both Windows and Linux suffer from the same UX shit show, horrible third party launchers are the worst problem with either set up.

Disclaimer: I'm involved in universal blue but don't directly contribute to bazzite.

The OS is delivered to you via a container (via the github registry), but can also run things in containers.

The OS itself is run on the bare metal.

Works if the developer enables it.

For example: Halo Infinite works fine, but Destiny and Call of Duty don't.

> On android this is pretty well integrated, what's the deal with desktop?

I have a button in gnome that toggles dark mode on/off that switches the desktop over that works for just about everything (not discord though).

I hope this helps explain it! https://www.youtube.com/watch?v=vZ1LRe_foJY

Not a tangent at all! https://gitlab.com/fedora/ostree/ci-test/ is the current location of the composed images we derive from.

That's what ends up on quay.io/fedora-ostree-desktops/ which is what we use to make our base images.

Fedora is in the middle of a transition to make more official images on quay.io/fedora, I'm sorry I don't have the info offhand, it's probably in here somewhere: https://discussion.fedoraproject.org/tag/silverblue/l/top?pe...

(Co maintainer here) Yeah this why don't call it a distro. It's just your scripts/ansible playbooks and then github runs "podman build" regularly and spits out an image at the end.

At the end of the day it's just running a build step in CI so that your machines just end up with the final image instead of running the playbook/script on each one. Hope that helps!

Thanks for the feedback we'll take a look!

We are fortunate to have the Fedora Asahi SIG to the enablement work: https://fedoraproject.org/wiki/SIGs/Asahi

There's stuff to do as far as making ostree/oci builds out of that but we're talking to folks regularly now so hopefully we'll get it sorted. Also a huge shout out to Equinix Metal for sponsoring an Ampere builder for us, hoping to get on as many ARM devices as we can!

Hi! I worked on this with some friends over the past two years or so (we had to work on the generic tooling first: https://universal-blue.org/)

I'm happy to answer questions you might have! Thanks for checking it out! (I'll be at KubeCon Chicago with stickers if you want the live demo on a Framework 13)

The article you linked literally shows you that the problem is a setting in the browser that needs to be fixed.

They do: https://thenewstack.io/apple-plans-to-run-most-of-its-comput...

> using separately-updatable libraries in the OS

There are separately updatable shared libraries via runtimes, they're just not managed by the OS (on purpose).

I find it ironic that the author mentions how much better watching Pink Floyd at Pompeii is better.

Roger Waters is probably salivating at the prospect of putting The Wall in the Sphere.

I'm familiar with endless (and their excellent team!). The current issue is that it doesn't support layering like Silverblue does via rpm-ostree.

I'd be awesome if there was a community effort around bringing the layering functionality and bootc enablement to all of Debian and then we could have our cake and eat it too!

You don't consume ostree directly like that, what happens is someone would make Debian ostree-enabled OCI images for users to consume and adapt.

https://opendev.org/starlingx/apt-ostree is one such effort to bring ostree to debian.

You don't know anyone who develops in containers? It's a pretty common pattern these days.

VSCode with the devcontainer and docker is great on Silverblue.

I've been prototyping some developer workflows with friends here: https://universal-blue.org/images/bluefin/developer-experien...

So far the major patterns are vscode with distrobox, vscode with devcontainers, vscode with devpod, jetbrains toolbox thing (which just runs everything out of the home directory, the OS doesn't care).

And then devbox/nix and homebrew in ~ is also an option if you're into that.

Distrobox and toolbox are developer tools, they explicitly are there as a convenience wrapper for podman/docker for development.

If you want hard separation you'd need a VM. It'd be awesome if you could just --firecracker on distrobox create and get that. :D

Your system should be cleaning up unused runtimes. That's perhaps a distribution integration issue that should be filed and fixed?

The disk space thing is a myth, once you start to install apps people actually use it ends up being about the same.

If you test it with VMs you can check it out for yourself: https://www.ypsidanger.com/wasting-disk-space/

I was lucky enough to work with Kris Nova. I was gutted when I heard this and I'm still in shock. She was in the middle of doing the hachyderm thing and I was struggling with some other stuff and we ended up just happening to meet at a restaurant. "Fuck what people say and think, do you what you want, that's what I'm going to do."

Here's a segment from one of her recent streams. This is how I will remember her:

https://www.twitch.tv/videos/1884973353?t=1238s

Nóva was a great friend and an asskicker, she loved being a hacker.

| but I seem to be in the minority.

Every time one of these threads comes around it's like the same thing on repeat: "I could either learn how to use a container or dist-upgrade my entire operating system to solve this."

ChimeraOS carried nvidia drivers for years. The issue is that Valve's Gamescope, which is now a requirement for Steam doesn't run well on the nvidia drivers, and old big picture mode got retired.

This is actually run my computer, with a fedora-silverblue based image but my CLI is running alpine images.

So I made a little kit so anyone can do this on any linux so you can try all the cool stuff in there without the downsides of running a less popular configuration on the bare metal.

And since it's Alpine it's always a fast download vs. a heavier container.

https://github.com/ublue-os/boxkit

I am finding an odd intersection of Kei trucks and geeks lately.

My friend imports KEI trucks and Vans for the mid Atlantic region and always has inventory: https://ohkei-imports.com

As it turns out a bunch of people want these things and he's been importing and shipping all over the US.

They're just catching up to Android, ChromeOS, and SteamOS. The market rejected traditional needs-a-sysadmin linuxes on client a long time ago.

The packaging format doesn't change source code availability or restrictions.

What are your concerns?