https://lwn.net/Articles/1040197/
People often ask “when will gccrs be ready?”, he said. It will be ready in one sense — building libcore, though perhaps not compiling it entirely correctly — by early 2026.
That doesn’t mean it’s actually viable though, but it’s slowly getting there.
dotfiles and system configuration are pretty different use-cases, usually when you do system-wide stuff you want to manage not just the configuration files but also what software is installed and a bunch of other things. Ansible or something else like it is definitely the right tool for the job. And Ansible isn’t so difficult to learn, you only need to know like 5% of what it can do to be very effective.
For dotfiles my personal preference is dotbot, but there are MANY many different tools that are all good and are just different ways to accomplish roughly the same thing.
Oh, that would have been really useful a year ago! Thanks, I’ll keep it in my bag of tricks, it looks pretty neat.
Yeah I wouldn’t call Arch a server OS. I run Arch on my laptop, but Debian on my docker/file/self-hosting server. Best tool for the job etc. Never even been tempted by Unraid, the whole point of running Linux is that I control what goes where.
+1 for Podman. I switched from docker last year and I’m really happy I did. It’s not all sunshine and roses (can’t copy paste so much from the internet being the main issue, nobody gives examples for it), but the product itself is much better.
This particular example isn’t very good, just install multiple kernels (or compile one yourself) on your distro of choice and boot into the one you want with your bootloader of choice. Once set up you don’t even have to change any configs any more, just use an interactive menu on boot. So even easier than NixOS? There are plenty of valid use-cases for Nix, this isn’t one of them.
You’re probably correct, although I have no experience with zram so can’t be sure. But you’re absolutely right that PostgreSQL depends heavily on the OS disk cache for optimal performance. Lowering the PostgreSQL setting like Blaster M suggests won’t improve performance much, since all that setting does is tell PostgreSQL’s algorithms how much memory is likely to be allocated to the OS disk cache. Of course it’s best if it’s accurate, so you’re best off seeing how much memory is actually allocated to disk cache under heavy use before setting it, but it shouldn’t massively reduce performance if you don’t get it right.
Check out carapace. It takes a bit of setup but basically tries to make all the completions work in almost any shell. For me that solved the big step backwards from fish’s completions that nu’s native completions have.
Yeah, it has. I think they started out as loving the concepts of PowerShell but hating the implementation, combined with the fact that PowerShell is clearly a Windows-first shell and doesn’t work so well on other OSes (it surprised me a lot to find out that PowerShell even has support for linux).
nu tries to implement these concepts in a way that’s more universal and can work equally well on Linux, macOS or Windows.
It’s arguably better as a scripting language than as an interactive shell. There are a lot of shell scripts out there that also dabble in light data processing, and it’s not the easiest thing to achieve well or without corner cases. So nu scripts are great if all you need is shell scripts with some data processing.
nu as an interactive shell is great for the use cases it shines at (like OP’s example), but a bit too non-POSIXy for a lot of people, especially since it’s not (yet) as well polished as something like fish is for example.
Edit to add that nu’s main drawback for scripting currently is that the language isn’t entirely stable yet, so you better be prepared to change your scripts as required to keep up with newer nu versions (they’re at 0.107 for a reason).
nu 's commands also work on JSON, so you don’t really need jq (or xq or yq) any more. It offers a unified set of commands that’ll work on almost any kind of structured data.
Or maybe all those things will work two years from now. And if some issues remain there’s still LTS support for a while in multiple distros, since this only affects future versions.