737 karma · joined August 20, 2016
https://steamcommunity.com/id/LennyMcLennington/
https://www.washingtonpost.com/wp-srv/national/longterm/unab...
[1]: https://www.reddit.com/r/PolyMCLauncher/comments/y6k4x7/swit... [2]: https://github.com/PolyMC/PolyMC/commit/ccf282593dcdbe189c99...
Also I am running into all kinds of problems every day with Windows and end up on Google all the time with way worse answers, no way to deeply debug most things and worst no way to fix them myself. I am way to often depending on some big capitalistic company to fix my problems and hope they feel like doing it. Linux is DIY capable. If I have the abilities and time to fix something I can most of the time do it myself.
Also to answer some of your questions: - you want to use Pulseaudio, alsa has no usecase on a desktop - and use vim or neovim if you are into plugins. vi is just an old editor which got replaced by vim.
Devuan only has one and only one selling point: not systemd, which makes it for most people a unattractive choice.
To correct your coffee snippet: nativeBuildInputs = [ pkgs.gcc ];
A python environment is effectively a different take on a venv. Python packages is one giant python environment. For programs that life outside of python packages but use the packages from there we are free to apply overrides how we want. So it is possible to have different versions of a package in a different python environment.
Right now in nixpkgs we manage all dependencies in all packages front to back. So all dependencies of a dependency and dependencies of dependency dependencies and so on.
I already posted multiple posts in the thread under the same username. Other than adding important consumers of a dependency to its tests, the only solution I could come up with is to move AI/ML packages into their own repository where they can move at their own pace and do pins/overrides more freely and/or drastically reduce the amount of python packages in nixpkgs.
I fail to understand how 2FA TOTP gives you junk calls?
SMS based 2FA is not effective but that's nothing new.
> Nix actually integrates all package updates into one channel which nobody else anywhere does
If you are using the python system packages then Arch, Debian and probably more are doing the same.
> it's even worse because a lot of projects use python as a build dependency (?!) which then cascades these issues even farther.
In practice this is not a problem at all. Build systems that use python underneath have usually very little dependencies. The bigger problems we are facing are big python (web) applications and anything that moves (very) slowly upstream like (sadly) many AI/ML projects.
FYI: I am very active NixOS maintainer and one of my foci is the python packages in NixOS.