_fsql

4 ms·

1.
by _fsql 2y ago
It's a reproducible thing, until the pile of crap in the abstraction layer they built with Nix on top of Linux fails for any number of reasons, whether they redefined a variable, removed it, direct flaws in the NixOS or Linux mechanism
2.
by _fsql 2y ago
Another fork, similar to what happened with other Linux projects regarding systemd. The difference is that in NixOS and now SixOS (SexOS), things are more dramatic, and they love piling up a bunch of complex and unnecessary crap on top of L
3.
by _fsql 2y ago
When it's finished and stable.
4.
by _fsql 2y ago
Sure, but tell me: How often do you see NixOS used as a file server, enterprise app server, in the cloud, as a web server, for big databases, email server, backup server, firewall, satellite server, in labs, banking, or critical mission ser
5.
by _fsql 2y ago
You shouldn't use something experimental like NixOS and Nix at work, that's fine at home or as a hobby.
6.
by _fsql 2y ago
The only thing missing from the article was to say that Ballmer loved Linux and open source but that he was misunderstood lol. Ballmer was a fucking despot and a piece of shit. That article is an ode to the disgusting despotism that Microso
7.
by _fsql 2y ago
If NixOS works well for you, that's great! But from my perspective, the whole NixOS model adds unnecessary complexity and makes you learn ways to do things that don’t really translate to other Linux systems. The directory structure in
8.
by _fsql 2y ago
No, I like it practical and without such stupid design choices.
9.
by _fsql 2y ago
Well, with Haskell you know what it is oriented towards and you know what to expect, but Nix wants to control everything in the system by adding unnecessary complexity to the simple and making the complex even more complex.
10.
by _fsql 2y ago
If Guix were an optimal solution, many companies would be using it, but that's not happening. It's just a niche experiment. And parentheses don't seem so bad when the code is one line, when tens or hundreds of lines won'
11.
by _fsql 2y ago
With NixOS, you simply use Nix to configure a file that in turn configures other files that configure other packages, and you have to rely on the new path and variable definitions created by the maintainers of NixOS for upstream programs. S
12.
by _fsql 2y ago
NixOS has very limited usage, with few companies adopting it for critical or commercial tasks. It is more common in experimental niches. One of the main issues with nixpkgs is that users have to rely on overlays for a package. This can lead
13.
by _fsql 2y ago
Guile and Nix are horrible languages with shitty syntax, the difference is that one is general purpose (Guile) and the other is a mix of yaml and json, while Guile (Lisp) abuses parentheses and you end up lost in spaghetti code, in Nix yo
14.
by _fsql 2y ago
NixOS is a terrible solution rather than a reproducible one. Adding a layer of complexity to simple text files that can be easily edited and having thousands of links that are links to other links is just stupid. Filling up disk space like