Yeah, who'd hate using a package manager that increasingly slows down your boot time with every package installed, or that uses a closed source store to provide you FOSS
Maybe there's a reason canonical has to force it on their users
Yeah, who'd hate using a package manager that increasingly slows down your boot time with every package installed, or that uses a closed source store to provide you FOSS
Maybe there's a reason canonical has to force it on their users
No, Debian doesn't take your apt install ...
command and install a snap behind your back...
So why should we use this instead of just saying lixmaballs and using nix/aux/nux/whatever other fork?
Prints a 10m scroll daily containing automated probes and attacks
When you do things right, people won't be sure you've done anything at all.
Damn you, the photo didn't load and I thought I'd be the first one. Time to start my own comment chain, with blackjack and hookers.
Dude still hasn't decided where to host the repo. It's not an alternative, guix is...
Wait a bit Ubuntu is next. They already added terminal ads, embedded affiliate links for amazon, and sold user data to amazon.
Installs proprietary WiFi drivers on Debian
PROPRIETARY OS
Try it, the worst thing that can happen is you waste a few hours, get mad, break your PC, and get a brain aneurysm
I've recently performed my first full conversion. The key was that windows took like 15 mins to boot and 5 more to open up chrome. That laptop might be ancient but with Linux it goes 0-browser in a minute, and the convertee is more than satisfied.
As you can see from the state of this thread, people see nix or nixpkgs but read nixos. There's no momentum from the community to push it as an extra package manager, while every thread is spammed with nixos.
No gui integrations for casuals. For example Discover integrates flatpaks and snaps, but for nix you need to use the terminal.
The documentation is abysmal. I spent days trying to figure out how to use nix as a declarative package manager before I accidentally came across home-manager. Even the manual leads you down the wrong path. A quick start guide with a few examples for home-manager and flakes, and a few basic commands, would've had me going in 5 minutes. That problem is made worse by the fact that almost all sources of info focus on nixos instead.
Edit:
if anyone's interested in trying it out, here's a part of my other comment in this thread
It's just a list of packages, and an optional flake to control the repositories (stable/unstable) and add packages from outside of the official ones.
To update everything nix related I just run:
cd ~/dotfiles/nix/ && nix flake update && home-manager switch
Best case scenario: sunk cost fallacy
Worst case scenario: there's a lot of shit you can do when you control a closed source app store, and canonical has a history of doing sketchy shit like selling user data to Amazon