jaxxed

All my homies use nerdctl anyway.

Switching colleagues over to Pdman desktop, whenever legal asks about licenses for DD. :)

Podman has some thngs rhat I don’t like but it ften works much better, and a lot f really great tools use it natively (like distrobox)

Plus he couldbhave just used ‘apt’ one command.

You sound like someone who thinks they’re representing a group, but are actually just being hyper-sensitve.

Tell me that you are offended and asian.

I am concerned abiut identifying myself on lemmy, but I will admit that I am not Asian, and that I don’t live in North America.

Why is it shit? If no-one is feeling hurt, what is the point? Are you protecting ppl or being hyper-sensitive.

If you are asian and offended, then tell me so, and I avoid using the term. I won’t even ask for proof or anything.

Are you? If you are Asian, and the term “ricing” offends you, then tell me so.

Because I dn’t think it’s hurtful. I don’t think it’s designed to hurt anyone, and I don’t hear anyone describing themselves as being hurt.

I will wait until Asian ppl comain in volume or academia before worrying about that.

Don’t you have a dark theme variant?

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)

It should be ~/.local/bin

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.

I’m not comparing it. I watched an interview with one of the openZFS guys, who talked about how engineering designs based on spinny things are hard to get to work on solid-state drives.

I had a FreeBSD niri setup that worked quite well for a bit. The jail-based containerd stuff was exciting, but not mature enough for my needs, so I had to leave it behind. Since then I’ve read lots of news about maturing wifi and ither improvements.

Graphics will always be behind, unforrunatrly; ZFS is starting to show its age too.

I think you have the wrong tone.

The comainers were nvidia, when they didn’t participate in the early anni g, and then cam in late trying to push a rewrite to the memory sharing model.

Was that just my fantasy, or did other people have the same drean? I did mention that I was an early adotper. Maybe I should have clarified that I never went back.

Listen, no matter your opinion on wayland, you can admit that some technical decisions made were not optimal.

The issue with wayland is that both the process and the base mechanisms had significqnt flaws, that made it take a long time to get things working. In all fairness, the core team uad a valiant effort for a dwcade, hampered by unresponsive complainers, and late-to-the-party suggestions.

Fyi: I am an early WL adopter, but not on any of the major DEs.