I really wonder how you managed to uninstall nix. Editing configuration.nix shouldn’t even allow for removing .nix…

Anyway, this post made me remember why I used btrfs for my new btrfs system.

Good idea to write a function, I’ll do that right now. Over the last few weeks I’ve been regularly doing the Ctrl+Z, bg, disown, which does get old pretty quickly. At least I now remember the terms and don’t have to search for them each time I need it :D

They are evaluating different ways to continue to support ad blocking. E.g. “unbraving” Brave Browser, or just implementing their adblock-rust.

They most likely won’t support MV2, since it would get increasingly difficult with each update to Chromium.

https://github.com/ungoogled-software/ungoogled-chromium/issues/662

Creating a wayland compositor based in wlroots is much more work than an X11 window manager. And then there’s quite a bit of work to keep up with new Wayland protocols.

But I personally don’t think there’s a need for more compositors, since the existing compositors do support all kinds of tiling.

E.g. river has custom layout providers, which allows for creating completely custom tiling behaviour. There’s even a hyprland plugin which implements river-layout-v3.

Removing nix is mostly done by deleting /nix, and removing some systemd services, as well as deleting some nix-related users or groups (iirc nixblkd)

Because almost all of nix happens in /nix it doesn’t clutter much of the system.

The I/O size is a reason why it’s better to use cp than dd to copy an ISO to a USB stick. cp automatically selects an I/O size which should yield good performance, while dd’s default is extremely small and it’s necessary to specify a sane value manually (e.g. bs=1M).

With “everything” being a file on Linux, dd isn’t really special for simply cloning a disk. The habit of using dd is still quite strong for me.