I can't speak for everyday workflow (having discovered this project less than a week ago), but rebase being unnecessary and cherry-pick not creating duplicate commits seem like the most notable advantages to me.

One thing that bothers me about Nushell (even if it doesn't really matter) is honestly just how bloated the table style is, with three columns in each column margin and six columns of enforced line numbers. Why can't it display tables in the same style as regular UNIX commands?

Another thing that bothered me is that the "blessed" way to parse tables from external commands seems very fragile to me. Iirc the builtin parsing commands work solely off table headers, which are locale dependent for many commands, so a script might appear to work fine but suddenly break if an LC_* environment variable sneaks in somewhere. The size filter trick works nicely for ls, but doing the same thing becomes painful again when using df.

I also found the script syntax (implicit line continuations, command seperation, etc.) difficult to understand but presumably that's just a matter of familiarity.

I'll have to give it another try in the future but for now Fish is good enough for me.

That's not entirely true, unless you choose to nixify everything. You can just have a basic Nix configuration that installs whatever programs you need, then use stow (or whatever symlink manager you prefer) to manage the rest of your config.

You can't entirely forget that you're on NixOS because of FHS noncompliance but even then getting nix-ld to work doesn't require a lot of effort.

Another alternative approach would be to add a duplicate desktop file, but to write it declaratively using Home Manager:

# in home.nix
home.file.".local/share/applications/firefox.desktop".source =
  pkgs.runCommand "firefox-desktop" { } ''
    cp "${pkgs.firefox}/share/applications/firefox.desktop" "$out"
    substituteInPlace "$out" \
      --replace-fail "Terminal=false" "Terminal=true"
  '';

# - or -
home.file.".local/share/applications/firefox.desktop".text = ''
  [Desktop Entry]
  Name=Firefox
  Icon=firefox
  Exec=firefox --name firefox %U
'';

It would be possible to DIY this with user activation scripts, but I don't really see a value in doing that over the symlinkJoin.

It's wild how on the orange website I can read entirely sensible discussions about tricky Bash semantics or whatever, while people in a parallel thread are seriously arguing the Trump admin's repressions are dwarfed by... whatever "repressions" they think happened during Covid. And I don't even click on the threads about disabilities (especially autism) anymore because it's so predictably sad.

I'm running KDE Plasma with the revived Krohnkite for auto tiling. Plasma 6.2 seems to have fixed most of the bugs from 6.0 and 6.1, at least the ones I've noticed.

I was using Sway/SwayFX for a few months but was missing some KDE Gear apps like Dolphin and Okular which I couldn't get to display correctly. KDE is afaik the only desktop with a working Qt theming engine right now, so I can't really see myself switching (unless maybe if they break Krohnkite again).

Also coming from Arch will induce a bit of a culture shock regarding documentation as the NixOS wiki is just... not very good. It's neither complete nor reliably accurate for the current release. And some wiki pages are actually just snippets with no explanation for either what they do or why they do it.

As a Home-Manager user I would argue it's not really worth it. It has it's moments for some applications but most of the time it's the same experience as editing the config files directly. Except instead of INI or TOML it's stringly typed Nix attrsets and you need to rebuild the entire system instead of restarting the app. Not exactly a huge improvement.

And that's when you're lucky enough that what you're configuring can be mapped to attrsets. Styling Waybar via Home-Manager means writing CSS but it's a multi line string in Nix with no appropriate editor support whatsoever, and writing custom actions for Nixvim means writing Neovim-Lua but... that's right, in a multi line string.

On a more positive note, I will second the recommendation for the NixOS & Flakes Book, I found it to be much more useful for getting my head around flakes (and Nix in general since I started using them fairly early on in my Nix journey) than e.g. Vimjoyer's videos, which are good but their repositories were really really cryptic to me at the beginning.

『合コンに行ったらイケメン女子がきた』/"I Went to a Mixer and a Handsome Girl Showed Up" by Murakami

Official Pixiv ^JP^ | Official Twitter/X ^JP^ | Mangadex ^EN^ | Dynasty ^EN^

I agree.

You could say that about any kind of autocomplete. Why would people install snippet plugins into their vim/emacs? Sure you can just type everything by hand but it's just more convenient.

Personally I find these kinds of inline AI suggestions make a more convincing use case than trying to prompt engineer a Chat based LLM and diverting your attention to phrasing specifics instead of the actual problem space.

TimeoutStopSec applies to the ExecStop command, TimeoutStartSec would be the culprit here. I'm not sure why there would be a default timeout of specifically 1:39 minutes though.