• 0 Posts
  • 109 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle
  • cerement@slrpnk.nettoLinux@lemmy.mlAny window manager suggestion
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    18 hours ago
    • main thing to keep in mind is that a window manager is normally just one component of a desktop environment – full desktop environments like Gnome go to great lengths to assemble a whole fleet of apps to work together to make a cohesive experience
    • if you’re going to forego the full desktop environment, then expect to have to fill in on the various missing pieces to suit your needs (file manager, terminal, text editor, clipboard manager, bar/panel/dock)
    • if you just want lighter weight but maintain a cohesive experience, then Xfce or LXQt
    • otherwise, there are a LOT of choices (both for X11 and for Wayland)
    • tiling window managers
      • i3 on X or Sway on Wayland are probably the most popular
        • special mention: Regolith – pairs Sway on the front end with Gnome components underneath
      • dwm for the full do-it-yourself experience
      • awesome if you like Lua, xmonad if you like Haskell, exwm if you live in Emacs, Qtile if you like Python
    • stacking window managers
      • Openbox for the old school feel, LabWC as the Wayland successor
      • IceWM and JWM for a minimal experience (both show up regularly on Raspberry Pi)
      • Motif for the retro enthusiast









  • with the majority here, I just use distro default / automatic setup in installer

    LONG ago, I did the whole hand-crafted thing, obsessing over exactly how large each partition had to be, but with increasing speed and lowering prices of storage, this attention to detail now seems pretty irrelevant:

    • hda split into /boot, /tmp, (swap), /, /opt, /usr, /var
    • hdb split into (swap) and /home






  • this is one of the things that struck me about email clients on Linux – CLI and GUI clients have followed two very different evolutionary paths – the CLI clients went for the “doing one job well” path (where you end up assembling a whole system of apps for sending and receiving email) and the GUI clients went for the “everything and the kitchen sink” path (where you end up trying to hide half the options so they don’t get in your way)





  • original generation of COBOL programmers where expecting their programs to be replaced (or at least rewritten) within a decade or so – and then Y2K and we realized how much COBOL was still in the wild – and now a couple decades down the line, they’re still having problems trying to convince fintech to switch from COBOL to the new language of Java …