No issues here, but I haven’t benchmarked anything and any improvement could be placebo. It’s trivial with flakes

You probably know this, but you can even run the CachyOS kernel on NixOS. Currently doing exactly that

Then why go against the AUR and not the official mirrors? The former isn’t always exactly the epitome of securely packaged trusted applications

Oh, that’s good to know.

I think this is a huge release of just because of accessibility, that’s always been a pain point (read: basically impossible) with LaTeX, I heard ConTeXt is better there but I never got into it. typst on the other hand is very approachable and makes a lot of sense.

While I don’t need accessibility very much nowadays, it’s basically a requirement for usage in the public sector here as PDF/UA. Which I guess is the main motivation.

Looking forward to trying it out when it hits my repositories, which should be soonish.

Another option is docbook, but I never particularly enjoyed working with that…

It’s too funny to me that Arch of all distributions attracts the thigh /Unix socks crowd (for lack of better word). Nothing about Arch stands out for me in that regard, there’s no social statement or anything, and when I was more active in the community, it wasn’t known for that.

I was deep enough into Arch to run my own private repository using aurutils, but no thighs :(

It doesn’t really do a lot for most people since you just skip UEFI initialization, which yeah does save a lot of time but you still need to restart all your processes

NixOS’ (which I ended up using) solution requires custom keys.

It was a contender when I switched, but its lack of Secure Boot options unfortunately disqualified it.

I actually considered it once. It failed in a VM but I probably tried too much fancy stuff at once (like replacing OpenSSL…)

To be expected, difficulty of Arch installation was always overblown, and Gentoo doesn’t have an installer either, but you need to handle stage tarballs while in Arch, you just used pacman

People are hating on Powershell way too much. I don’t like its syntax really but it has a messy better approach to handling data in the terminal. We have nu and elvish nowadays but MS was really early with the concept and I think they learned from the shortcomings of POSIX compatible shells.

Also DXVK, though the period of time where DXVK existed and Proton didn’t is rather short (a little bit more than half a year).

I haven’t watched the video, but maybe it wasn’t in bad faith, but the author didn’t know better. bash can be arcane at times, like when I open my old scripts I often have no clue what exactly is going on without comments. Substring removal comes to mind.

I’m not even sure what strucrued data would really mean, so I’m pretty sure it’s not useful to my usecase lol

Probably not, but to give an easy example:

~> ls | where modified >= (date now) - 30day
╭───┬───────────┬──────┬────────┬────────────╮
│ # │   name    │ type │  size  │  modified  │
├───┼───────────┼──────┼────────┼────────────┤
│ 0 │ Downloads │ dir  │ 4,0 kB │ 4 days ago │
│ 1 │ Musik     │ dir  │ 4,0 kB │ a week ago │
╰───┴───────────┴──────┴────────┴────────────╯

Here, ls doesn’t just return a string representing directory content as text, but a table where each file is an entry with attributes that have their own data type (e.g. size is Filesize while modified is Datetime). That’s why I’m able to filter based on one of them; that part isn’t part of ls, but of the shell itself. In a classic shell, this filtering would need to be handled in the originating binary in its own specific way, or you’d need to parse its output, transform it using tools like sed and awk etc. This here is a special case because ls is built into the shell; for non-builtin commands, if they offer it, you can have them output structured data as json or something else and read it into nu, like

~> ip -j a | from json | where {|device| $device.address? != null and $device.addr_info? != [] and $device.link_type =~ "ether"} | get addr_info.0 | select -o local broadcast scope
╭───┬────────────────────────────────────────┬─────────────────┬────────╮
│ # │                 local                  │    broadcast    │ scope  │
├───┼────────────────────────────────────────┼─────────────────┼────────┤
│ 0 │ 192.168.178.72                         │ 192.168.178.255 │ global │
│ 1 │ 2001:9e8:4727:2c00:3071:91ff:fed1:9e26 │                 │ global │
│ 2 │ fdaa:66e:6af0:0:3071:91ff:fed1:9e26    │                 │ global │
│ 3 │ fe80::3071:91ff:fed1:9e26              │                 │ link   │
╰───┴────────────────────────────────────────┴─────────────────┴────────╯

It’s kind of cool, but I don’t need it that often either, so I just play around with it when I feel like it.

I’m glad you mentioned nushell (it sounds like) is a more poweruser thing.

It serves a different niche. nushell is very good for working with structured data. fish on the other hand is a “conventional” shell that’s not POSIX compliant. I guess that’s why they call it “a command line shell for the 90s” because it doesn’t incorporate modern concepts, it’s just more convenient than POSIX shells.

This results in some notable differences: nushell for example has actual data types (https://www.nushell.sh/book/types_of_data.html, though they are dynamically typed by default).

All this doesn’t mean that one is better than the other. I use fish daily and just sometimes dabble in nushell because most of my workflow doesn’t require all the stuff nu offers.

Oh yeah, I never used Python myself and did some very simple (but IMHO too much hassle in bash) Go stuff some time ago. It’s a really good language for that, and if you can’t build on the target, the binary is statically linked anyways.

What’s so bad about string replace World Bash $STRING?

Just don’t microwave it.

Same, but I don’t think it was ever intended differently; I mean the word interactive is literally in the name. If you want portable scripts, use bash. For simple helpers, quickly define a function. If you feel your script becomes too long, use Python.

None of this stuff for me. I prefer one tool doing one thing, like busybox