she/they
Nu’s find builtin isn’t a GNU find repacement. I think what you actually want is ls piped into where:
ls **/* | where type == file
I do question the choice to alias a well-known program with a builtin that does something entirely different. You can also use ^find to avoid calling the builtin. I would’ve expected \find (bash-like) or command find (fish-like) to work as well, but alas…
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.
No C program is written to satisfy a borrow checker and most wouldn’t compile with one, so adding it would require rewriting the world anyways. At that point why not choose a language that, in addition to being memory safe, also drastically cuts down on other kinds of UB, has sum types, sane error handling, a (mostly) thread safe standard library, etc.?
The mentioned performance governor runs the CPU permanently at maximum frequency, which is obviously bad on battery powered devices and on devices with lacking thermal headroom. I think it might cause problems in virtualized environments as well but I’m not sure about that.
To be fair showing the overview on startup makes perfect sense on vanilla gnome, it’s only dumb if you install one of the two specific extensions that partly replace it.
Running poweroff is one of the correct ways on anything Systemd (details). If that doesn’t work then something is broken.
If you haven’t done so already try looking into the journal. sudo journalctl -b -1 -e will take you to the end of the log for the last boot.
I am very sorry to remind everyone about the existence of Visual Basic, but it has:
And I know what you’re asking: Yes, of course all of them have subtly different behavior, and some of them only work in VB.NET and not in classic VB or VBA.
The only thing you can rely on is that “\r\n” doesn’t work.
GUIs do have advantages in things like discoverability. Honestly the 1983s Apple Lisa nailed this with the idea of having clickable menus annotated with keyboard shortcuts, so users could do the same thing faster next time. For some reason we stopped doing this (especially in web apps), but that’s a reason to make better GUIs, not to RETVRN to the feature set of a VT100.
I don’t know why we have to go on nonsensical diatribes about “UNIX wizards” though when we’re fundamentally talking about a handful of minor UI improvements to things that already exist.
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.