4 ms·
i find myself conflicted: - on the one hand you have the general warm fuzzy feelings associated with a considerately-designed graphical tool to lower a barrier
by 0x69420 3y ago
i find myself conflicted:
- on the one hand you have the general warm fuzzy feelings associated with a considerately-designed graphical tool to lower a barrier to entry
- and the fact that this tool was as trivial to implement as a cursory glance at the repo suggests vindicates the whole guix/nix declarative packaging idea. the ease with which ten lines in a text editor turned a new piece of software into a first-class citizen on my system was the thing that hooked me on nix forever
but that's just it: is this really lowering the barrier to entry all that much? the audience guixsd/nixos is courting is someone sick and tired of managing config files strewn across the filesystem. by definition that is someone who knows how to operate a text editor, at which point "look at how few keystrokes/memorised file paths you need on our system vs debian/arch/whatever to gain the same thing" feels like enough of a sales pitch
in terms of attention economy, this is like going "what costs you a dollar on debian costs you a dime here... hey check this out now it's 9 cents if you want. neat, huh?"
- Guvante 3y agoWriting your first one can be brutal. While using pre-existing packages can be super easy the syntax to make a package is not.
- James_K 3y agoI can see myself using this even though I know how to do most of this stuff. I don't have the exact syntax of a package memorised and I think this is probably the easiest way to write one. It doesn't have to be revolutionary, just convenient.