Inb4: I have used Linux exclusively from 2019 to 2024. It wasn't that bad but it wasn't flawless. At least once per month I met some issue that took few hours to solve. Currently on Win11, zero problems (yes, I am using pirated LTSC IoT version, how did you know?)
As everyone knows, Windows has its own fair share of issues. The first is that it is not a Unix :).
And I do not miss at all the Microsoft bullsh*t on tracking and advertising. Or the general sluggishness of Windows.
Early this year I bought a ThinkPad T14 Gen 5 AMD. In contrast to when I had a T14 Gen 1 AMD early 2020s, everything just works. All the hardware works, suspend/resume works, all the hardware comes up after a resume, etc.
Lately I have been using my ThinkPad much more than my MacBook Pro. NixOS is a superpower to me and having NixOS on a laptop is living the dream.
You were here for the really hard stuff, and missed the beginning of the good times, I think. Unlucky! Oh well. Welcome back!
I have also used headless Linux machines throughout my Mac vacation :).
With regards to the hard stuff. 1994-2007 was from my 12th to my 25th, basically overlapping with when I was a high school/university student. So, plenty of time and not enough money for a Mac or some commercial UNIX system. That period was also super exciting, especially up till the dotcom crash a lot of people thought that Linux was going to take over the desktop (anyone remember Corel Linux and even WordPerfect on Linux?). Linux did take over, but in different ways than we imagined, the server was kinda expected after the mid-nineties, but Android not.
Can you expand on this? Just curious what is the main value-add you are getting from NixOS in particular?
- Great modules for programs/services in NixOS and home manager. So I typically do not have to figure out what configuration format something uses. Most common options are exposed as module options and for options that are not exposed, it's often possible to write the configuration in Nix (or worst case a string that gets added to the configuration). I can access the documentation of all modules with a simple _man configuration.nix_ or `man home-configuration.nix`.
- I can override arbitrary packages with custom build options, etc. I don't have to maintain separate .spec/rules files or anything. I can just put a somePackage.override/overrideAttrs somewhere in my system configuration and the package customizations are there with my system configuration and always get built with the system.
- Packaging something to hook it up in my system is low-effort. nixpkgs is the largest distribution package set (according to repology). But sometimes something is missing or I want to add some of my own projects as packages, unless it's some insanely bad proprietary application, I can do it in a few minutes.
- Atomic updates/rollbacks.
- Ad-hoc or project-specific development shells (though that is more Nix than NixOS).
I know that the learning curve can be steep, but once you really get Nix and NixOS, it's kinda like being the master of the universe, erm, I mean your systems.
I might try it again. Last time I really did not like that any minute config change would take 15s to apply.
But the biggest issue for me, is that right now I have a good enough solution, that allows for config file update from applications. I have a small git repo, with one shell script, that symlinks config files, and even generates a few. And so backing up the latest config changes from KDE, freecad, etc, is a git add & commit away. I have another shell script to setup the base Ubuntu the way I want. And my data is replicated via syncthing.
Also it isn't as if I haven't subscribed to Linux Journal during its whole lifetime, or LWN, or even used to write M$ on email signatures and Usenet messages, for that matter.
Signed someone that knows Linux since kernel 1.0.9, yet has better things to do than making it work.
Slapping Linux on a Windows box is a mug's game
This kind of discussions are so repetitive.
They also seem to really care about supporting Linux. E.g. WWAN modems need proprietrary unlock procedures these days thanks to the FCC [1]. Most vendors would shrug and say 'sorry, we only support Windows', Lenovo has a repo with Linux support for all the modems that ThinkPads support (you can only use supported modems, because the FCC apparently only certifies laptop/modem combinations, not individual modems):
And exactly the same experience with OEM vendors that were supposed to be Linux friendly, on my case the whole netbooks effort, where graphics, video decoding and wlan never worked as well on Windows, even though they were supposed to.
Dell XPS also had their issues for something that was supposed to be Canonical certified as running GNU/Linux properly.
It seems Android, ChromeOS and WebOS are the only ones where OEMs actually care to make it work properly, naturally the cloud and IoT vendors with their custom distros as well.