Cool so this article calls out various types of coupling and offers no strategies for managing it.

Waste of time.

It’s so ironic how many downvotes this is getting in the context of this thread.

Well I guess I can give my opinion as a former VSCode and Vim user that migrated to Helix. @shadowedcross@sh.itjust.works was curious too.

Way back when, I used Sublime Text and got proficient with those keyboard shortcuts. Then VSCode eclipsed (pun unintended) Sublime, so I switched and I was thankfully able to keep using Sublime key bindings. I was also productive with VSCode, except it wasn’t popular at the company I was working at, where most people used Vim. I ended up learning a bit of Vim for pair programming, but I still clinged to VSCode, even though it lacked proper support for connecting to a VM via SSH (which was a very common workflow).

At some point I realized that it was important to have a totally keyboard-centric workflow to level up my productivity and ergonomics, and being able to use a mouse in VSCode was hindering my progress. So I tried NeoVim, and it was kind of a nightmare. I know many people enjoy tinkering with Lua to get NeoVim working as they want, but I found it more of a barrier to productivity than anything else.

So then I learned about Helix, and it seemed like a love letter to devs that just want a modal in-terminal editor that works out of the box and has modern features like LSP support, DAP, etc. Also it’s written in Rust by good maintainers. I haven’t looked back, because the Helix + Tmux combo is incredibly versatile.

I think it mostly has to do with how coupled your code modules are. If you have a lot of tightly coupled modules/libraries/apps/etc, then it makes sense to put them in the same repo so that changes that ultimately have a large blast radius can be handled within a single repo instead of spanning many repos.

And that’s just a judgement call based on code organization and team organization.

This reminds me of the apparent gnome-keyring security hole. It’s mentioned in the first section of the arch wiki entry: https://wiki.archlinux.org/title/GNOME/Keyring

Any application can read keyring entries of the other apps. So it’s pretty trivial to make a targeted attack on someone’s account if you can get them to run an executable on their machine.

There’s also the Wayblue family of Wayland distros, based on Ublue.

It’s hard to say for certain whether a distro will work for your hardware, even the Nvidia-specific images can have bugs related to the Nvidia drivers or their interaction with compositors.

I’ve used NixOS for a year.

I also tried Fedora Sway Atomic for a week or so. It mostly worked well, but I eventually found that it’s really hard to use Nix for development on a graphics application, because linking with the system Vulkan drivers is near impossible. The loader used by Nix’s glibc will ignore FHS locations. That seems to rule out a lot of the benefits of using Nix.

So I gave up on using Nix + Fedora as a failed experiment and went back to NixOS.

My wish list for Nix, Wayland, and Sway is pretty long. I kinda wish I had the time to make a new distro.

I just don’t support dogmatic thinking and indoctrination, especially when it creeps into politics, which is inevitable at the scale of the most popular religions.

In theory I have no problem with other people’s faith, but in practice it degrades the critical thinking capacity of our population and, paradoxically, the moral capacity as well. That’s a net negative in my opinion.

Charities exist without religion. I think religions often teach good moral frameworks, though very traditional. But those come with a huge caveat that you cut out a big hole in your brain for the belief that God exists and cares about how you behave. That one idea leads to so much trouble, from false prophets to normalized misogyny and hatred of gay people.

They are arbitrary but they at least serve as marking posts for real generational trends. I’m not sure there is much benefit in trying to find any categorization that isn’t arbitrary, so long as the generations are large enough.

So I’m seeing “Window Protocol: wayland” in about:support. Seems like somehow I’m just not affected by this issue.

Potentially Wasted

Ranglin’ Pangolins

Away from PC for a while but I’ll check when I’m back.

Interesting. I am not having any issues with Firefox. Maybe I’m already running in XWayland somehow?

After a little more time with it, I’ve noticed that nvidia + sway is causing a lot of flickering on updating rectangles of any window, presumably from a compositing issue. I expected the “explicit sync” fix in the 555 Nvidia driver to fix this, but I’m currently running 555.85. I hope it’s not some other issue.

So right off the bat I tried rebasing from Fedora Sway Atomic to the Wayblue sway-nvidia image, but I got the error:

Package 'rpmfusion-nonfree-release-40-1.noarch' is already in the base

I think because I had previously tried installing nvidia drivers from RPM Fusion. So I reset back to the base image with:

rpm-ostree reset --overlays

After that everything went smoothly and I’m apparently booted with a functional Nvidia driver. Thanks for the help! I’m off to try running some graphics.

Oh thanks! I didn’t notice “Sericea” was the name of this image when I installed it. Wish that had been more obvious.

Wait. Where are you finding the sway image? I’m browsing the images but I don’t see it.

EDIT: Maybe it’s only Way blue that has sway?

Oh I didn’t realize they had one with Sway. That helps!

Buy a portable AC unit and install it in your bedroom or living room window.

EDIT: I have this one that works well at least on a single room: https://www.amazon.com/Vremi-000-BTU-Portable-Conditioner/dp/B084H4B6NB?th=1

Thanks! I had seen the ublue template, but not that blue build tool. Will check it out.

Gotcha, lack of docs is tough.

Ideally I would use an existing atomic distro with both Sway and Nvidia drivers, since I’m currently failing to install those drivers without getting black screen on boot (the issue).