Let’s cooperate!
i think the question is valid: it seems strange first, but the cli-env. is so MUCH MORE POWERFUL.
lynx (when possible), fff, cmus, mutt, latex, core-utils, mupdf (vi like keybindings), sxiv, mpv (no-gui)
i only use gui programs if no cli option exists: js-browser, gimp
… and that is why the average user stays an average user.
Hey, i wanted to ask that!
why not curl? it also supports gopher 😉
https://en.wikipedia.org/wiki/Unix_philosophy
“…This style was based on the use of tools: using programs separately or in combination to get a job done, rather than doing it by hand, by monolithic self-sufficient subsystems, or by special-purpose, one-time programs.”
The more you learn about the original vision,. … it is kind of terrifingly brilliant and powerful. The architects knew exactly what they were doing. That’s why in the late 70’s they tried the keep it from the public! (you can send thx to rms - he opened it up for us)
Sure, systemd does what it is supposed to do. It is NOT bad design from the admins perspective, but from a os-architecture perspective. It is a huge single binary with a huge number of 0-day exploits (you can check those). The scale of the projects causes many possible exploits. A set of small programs, which do only one thing, is easier to maintain (^= decentralization of os-design)
There is not a scientific proof YET, but i think it can be done: for that we would need to program the “corner-stone”, which would be the *nix-program #1 - something that could show practically what the pioneers of the *nix system envisioned. This practical proof is possible, if we deep dive into the POSIX definition to analyze for what it was made.
unix is a trademark, but what counts is the architectural vision behind it (D. Richie&co.) I think it would be better to avoid the tradmarked word (sry for using it) - *nix may be a proper word (although it implies that it is a whole group)
It’s bad design and therfore a wrong standard. Also, it’s a security desaster.
the *nix system up to the shell enviroment needs to be clean, libre and true to the vision - everything beyond may be. … whatever…
I think the init system matters A LOT! Systemd is anti-unix-style and making it a “new default” and forcing it, by depending on it, is breaking the best os-design there is: the unix-like system. (who changes it will be forced to reinvent it…better stay close to the original vision in the first place)
If you’re into kernel hacking, you may consider supporting the HyperbolaBSD project, which seems much more promising than hurd.
Hyperbola has the best vision for a clean and libre general-OS.
Yes, they very strict about the interpretation of “libre”, but that makes the vision pure and crystal clear.
More information: roadmap
https://wiki.hyperbola.info/doku.php?id=en:manual:contrib:hyperbola_roadmap
some more tips:
· use bash key bindings and bind them to smt. like:
vim $(find ~/my-project | fzf)
· dmenu with a wrapper that sources an alias-file