• 1 Post
  • 37 Comments
Joined 1 year ago
cake
Cake day: October 12th, 2023

help-circle



  • Starting anything from scratch is a huge risk these days. At best you’ll have something like the python 2 -> 3 rewrite overhaul (leaving scraps of legacy code all over the place), at worst you’ll have something like gnome/kde (where the community schisms rather than adopting a new standard). I would say that most of the time, there are only two ways to get a new standard to reach mass adoption.

    1. Retrofit everything. Extend old APIs where possible. Build your new layer on top of https, or javascript, or ascii, or something else that already has widespread adoption. Make a clear upgrade path for old users, but maintain compatibility for as long as possible.

    2. Buy 99% of the market and declare yourself king (cough cough chromium).









  • My experience with pacman was via rwfus on steam deck. I was coming in as someone with experience with apt, npm, pip, even choco and winget on windows. My expectation from pretty much every other command line tool is that commands are verbs, flags are adverbs. So having to install with “pacman -S” (or is it “pacman -Sy”?) just feels unnecessarily cryptic. Same with “nix-env -iA”. I understand that there are some clever internals going on under the hood, but you can have clever internals and sane defaults. For instance, “npm install foo” both downloads the package to node_modules and updates package.json for me, so I can see what change was made to my environment. Nix should do that.





  • pacman and nix are both really neat conceptually but they both fail at the most obvious usability test, which is “I just want to install a package”; its like exiting vim all over again.

    edit: yes, I know you can set an alias to pacman -Sy or whatever, but if you need to set up an alias for a command to be usable, then I can’t in good faith recommend that OS to anyone, and I don’t want to use an OS I wouldn’t recommend to others.