stelcodes

You're welcome! Thanks for the kind words.

Thanks for checking it out! If you'd like you can post your blog link in an issue or discussion once it's up and I'll link to it from the MultiTerm README. :)

For anyone on Fedora 36 wanting to play with Ardour 6.9.0 with some awesome free effects and synth plugins, try this:

  sudo dnf install ardour6 lv2-calf-plugins-gui ladspa-autotalent-plugins lsp-plugins-lv2 lv2-zam-plugins lv2-synthv1 lv2-amsynth-plugin

All the plugins will automatically show up in the plugin manager!

Hi Paul, just wanted to say thanks for working so hard on Ardour. I just started playing with Ardour in Fedora on my Framework laptop, but I've been thinking about buying a M1 mac to make music because I miss Logic and Ableton. These release notes have got me hyped because now I might not want to! I'm very excited to try out the clips and freesound features. I'll definitely be buying a license soon. You (and the rest of the brilliant Ardour contributors) seriously rock!

WRT Home Manager, that makes sense and portability is definitely a cool benefit of Home Manager. But keeping all of your config for multiple workstations in one has drawbacks too. I found myself frustrated when I wanted to install something but I forgot to push changes from another computer so I needed to stash or rebase later on. Just to install a package! I only have one workstation and a small amount of servers, and I tried running NixOS on everything. It worked well (I still have multiple servers running NixOS actually) but for me, the benefits just weren't worth the overhead of living full time in Nix land. Now I use Debian stable for new servers and I prefer it. But yeah, lots of personal preference here. And WRT nix-env, it seems troubling to me that the fundamental tool of the Nix CLI is something that you recommend people stay away from. I think you may have be right about that recommendation, but I think it shows that Nix as a product is far off from being a "pick up and run" tool for average developers. I really hope that it will somehow get to that point but, like the author says, I don't think it will be Nix itself because it has burrowed itself into a bespoke, complicated UX that has a huge learning curve. I like simple things with elegant UX so that's where I'm coming from. There's just so many ways to use Nix, like, TOO many ways. But I'm glad that they're pioneering this space.

I used Nix and NixOS for more than a year as my daily driver. I've contributed to Nixpkgs. I agree with the author on most if not all of their points. Here's some advice: If you're interested in Nix, take steps not leaps. Use the Nix package manager. It's a great addition to distros like Debian. Then maybe use Home Manager (even though I think Home Manager is way over-hyped, see below). Then write a bunch of derivations. Then go learn the ins and outs of systemd. THEN go play with NixOS. If you skip any steps before the NixOS part, you will get lost in the weeds. The happy path of NixOS is very happy. The other paths are very challenging. You should really know a lot about both Nix and more traditional Linux packaging methods before you go all in on NixOS. And honestly, learning more traditional Linux utilities is a far better use of your time than learning the complex, ever-changing Nix landscape. It's a super cool project, I'm so glad it exists. But it should really be viewed as a _research_ project. Many good things will come out of it. Hopefully one of those things (like the author mentions) is a Nix clone written in a common language with a much better UX. Until then, try to avoid the urge to play with shiny things and stick to just using the Nix package manager and more traditional tooling.

And about Home Manager, the reason why I think it's over-hyped is because it provides a declarative approach to something that was... already declarative. Your $XDG_CONFIG directory does not need a leaky Nix abstraction on top of it. It actually just makes everything 10x harder. The Home Manager Nix abstractions are terrible but people seem to love it? Why would I write my i3 config in Nix?? An i3 config literally cannot get any simpler. Why make it more complicated for no benefit? I also don't need a declarative list of all installed packages. I'd rather just use `nix-env` personally.

Oh I was just chiming in really, not trying to say anything about copilot

Yep, same. Speaks volumes!

I mean, Clojure kinda does that

Wow that’s fascinating. I’m glad I care more about building software than language purity

I feel like Clojure companies should be on here too as it is very much a LISP

Ive thought about this too! That seems totally possible. I think that’s such a great idea. It could truly bring Linux to the masses!

Doesn’t every declarative tool require some new learned syntax? The Nix language is pretty damn good at configuration IMO. It is significantly less complex than python, for example.