Nix sounds like a great idea wrapped in an utter garbage implementation that everyone refuses to fix because of the sunk cost.
-
Nix sounds like a great idea wrapped in an utter garbage implementation that everyone refuses to fix because of the sunk cost. Just layers of more confusing subtools.
Everyone who uses it speaks like a battered housewife. They talk it up and then accidentally let slip all the utterly insane things they had to do to learn it and get it to work. The community also has a weird Dark Souls-esque Machismo around it too. Just gotta get gud at Nix, son. -
Nix sounds like a great idea wrapped in an utter garbage implementation that everyone refuses to fix because of the sunk cost. Just layers of more confusing subtools.
Everyone who uses it speaks like a battered housewife. They talk it up and then accidentally let slip all the utterly insane things they had to do to learn it and get it to work. The community also has a weird Dark Souls-esque Machismo around it too. Just gotta get gud at Nix, son. -
@NullNowhere I expect that after the alternative implementations make more progress on fixing bad design decisions and breaking backwards compatibility, they’ll start on the language itself. Until then…pain.
@speckledlemon@urusai.social the whole thing just stinks of Cmake. They’ll just have a hell of spaghetti recipes and tech debt no one will be willing or able to fix because Nix has that makefile problem (“I don’t know how to write make, I just copy other Makefiles”) that is deeply entrenched given the poor documentation. They’ll have 10 different style of recipe file that they’ll have to support.
It just feels like it’ll be pain forever.
