[–] 1 point 2 years ago* (last edited 2 years ago)

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

  • source
  • [–] 4 points 2 years ago* (1 child)

    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

  • source
  • [–] 2 points 2 years ago* (last edited 2 years ago)

    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)

  • source
  • parent
  • context
  • [–] 6 points 2 years ago* (last edited 2 years ago) (1 child)

    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)

  • source
  • parent
  • context
  • [–] 3 points 2 years ago (3 children)
    1. 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.

    2. 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)

  • source
  • parent
  • context
  • view more: next ›