Negativity around the graphical installer

I agree. Having been a Linux user for almost two decades, having tried Linux from scratch already, I never really got into Arch or Gentoo as their installation experience back in the day was too far off the beaten path. But as I gained experience in software development, particularly with infrastructure is code, eventually learning of Nix through tech blogs and YouTubers: its novel declarative premise resonated with me, and the graphical installer lowered the friction for onboarding and adoption.


Indeed, this is definitely how I’ve been propagating my NixOS config onto rest of my systems thus far. I can also see how giving the user an opportunity just before clicking the final install button to alter the nix config directory prior to deployment would be advantageous for same experienced users as well.

1 Like

Well would you look at that, someone went and made a Terminal installer: Nixos-wizard: a TUI installer for NixOS

1 Like

A TUI is still a UI… it’s not inherently Superior :tm: for running out of a terminal window (it’s likely worse in many areas like accessibility). A UI-based installer will never capture all use-cases, but it better at least handle the standard use-cases extremely well. Is there a reason to use this project over calamares?

No idea if it’s better than Calamares, I have neither tested it nor reviewed the code behind it, but it is in active development, last commit was 5 days ago.

And yes likely it’s worse in terms of accessibility, I just brought it up as a different UI based installer, an alternative, may have done stuff better in some areas than Calamares, no?

Edit: Calamares last commit was 3 months old while the src was 4 months old, not outdated nor abandoned, but I wouldn’t call it in active development.

Brand new codebase has more recent commits than low-churn established codebase. News at 11?

(Also note the GUI installer was merged into nixpkgs a few days ago with some significant improvements, including the qt6 update. We will be archiving the old repo).

2 Likes

If anyone can point to something concrete, we should consider adopting something similar in the official. Otherwise, eh.

Fair enough, I know too little of both to make a fair comparison.

Last commit pushed to the default branch was just two weeks ago:

I’m guessing you looked at their GitHub repo, which is still hyper linked to by the project’s website.

I was also confused when I couldn’t find the release notes for the version delineated in the mentioned nixpkgs PR, until I noticed the src was fetching from a different url.

@ruffsl They were talking about the calamares-nixos-extensions repo

1 Like

Yeah I didn’t look deep enough, I went searching for the Calamares page, then follow the link to Github page, which lands in this repo, it says last commit was 3 months ago (maybe there’s a more recent branch?): GitHub - calamares/calamares: Distribution-independent installer framework

That’s on me, the README does mention it was migrated to codeberg, they should redirect the old calamares site to the new one: https://calamares.io/https://calamares.codeberg.page/

Given that, they’re both in active development and Calamares should be more mature, you can disregard my comments.