jaxxed

I should add rhat it is very easy to extend the immutable os usong a short dockerfile, if your tooling is so important that you want it in the immutable layers.

Distrobox or toolbx are the canonical dev environment approach (persistant containers) but bluefin also comes with linuxbrew for host level tooling. I actually use mise (mise en place) instead.

We should note that it is super easy to extend a bootc release, and use dnf to install additional packages. It is a docker/podman contanerfile of a few lines.

I have a github repo that adds virtmanager and ghostty to the excellent zirconium release, rebuilds ever day - and then uupd pulls the update every day.

The atomics are not meant to limit you, they are meant to free you to get what you want, usng simple oci tools.

Another great thing is being able to swap distros with simple commands. I installed bluefin, then swapped to zircnium to get niri and dms.

I bet you can install a pipewire-pulse package, and it will repkace your pulse installation (I have no debian experience)

Can you comment further on the three mesh networks rhat you use?

I only use zigbee, but would consider branching out

I don’t understand the helix approach.

Let’s build a new editor in rust (good), that is in the legacy of vim/nvim[/emacs] (good), that moves to resolve the backwards mechanics of the vim-syntax like meow (good) … but let’s build it all as built in features with no modularity ???

How can you build a new terminal editor like vim/nvim/emacs without realizing that the core strength is that the best features are delivered in plugins. Why would you try to write all of the functionality yourself? Why would you think that a small team can handle all of the work? How can you not realize that external contributors in vim/emacs are the source of the most interesting functionality?

I liked helix, almost as much as emacs w/ meow, but yiu xan’t extend it, or write a plugin.

That’s not the really weak part of immutable OSes. The really weak part is that they are not immutable, they aren’t even locked down for /usr/local/bin.

You have to work just as hard to audit an immutable os.

You could shut down your vm service temporarily and see if it works.

To clarify, systemctl stop libvirtd should do it.

Is there no reason to suspect your vm states are the cause?

Have you tried “niri” wm? Pair it with dankmaterialshell or noctalia-shell for a desktop feeling (cosmic is also and option.)

The keyboard based control you are looking for is almost met, but not quite. That said, you might find this kind of a navigational wm works well for you, based on your description.

The niri website has a decent video demo.

HA install is incredible easy, but SSL is tricky.

Does river have a niri-like scrolling layout handler yet? (One where windows don’t resize when new windows are generated)

Honestly, in the long term it has been less effort.

If you’re an “out-od-the-box” comouter user (web browser, maybe one or two apps, and office suite, then stick with the more conventional distros. If you are very dynamic with your OS, especially 8f you play with a lot of different OSS applications, then Arch get’s easier.

I am thinking of different “theys”. I am not wait8ng for steam to give me a desktop. I am not waiting for kde to take this seriously.

I am hoping that some of the very talented teams that manage small wms, who come up with interesting ways to interact with your apps, to get interwsted in tue developer kit.

I think that I said it above, that I think that paperwn / niri / karousel are the best starting points.

I tuink that I understand what steam is selking, but I don’t think that a windowed wm is ideal as a desktop with VR. I get that we are takking about a computer strapped to your head.

The karousel guy could take a stab at it, but if Steam releases a dev kit, then any team could try developing a wm with workflows that are designed around a VR interface.

They’re releasing an SDK, which most likely will include a linux compatibility. Windowing desktops may not be the right starting point for a VR desktop, but hopefully some of the teams will grab the developers kit and consideration VR centric ways of working with applications.

are there any linux WMs that provide a good desktop experience with VR headsets yet? I’d love to get a niri like scrolling experience with goggles - although it would make meetings weird.

Which surface do you use? And what features are missing still?

Not an expert though, but have been watching bcachefs for … what feels like a decade.

It’s marked as experimental, hence the “experimental”