[object Object]

Autocorrect hates me, I am sorry.

  • 0 Posts
  • 68 Comments
Joined 1 year ago
cake
Cake day: July 20th, 2025

help-circle
  • I really like the terminal, most of my use is a web browser or terminal with tmux.

    I use hot keys like cray, but I haven’t found a timing window manager I like yet (I don’t like when things shift automaticallly, it breaks my mental model), and I haven’t found a Linux desktop with the keyboard ergonomics of macOS.

    But 95% of my time is with full screen terminals, so I’m actually pretty okay. I have customized vim and tmux to the hilt, and I like that.










  • If you install home brew 90% of the issues go away.

    The problem is that most Linux software assumes it can do whatever it wants, and immutable distros do not let you write to the system files.

    This creates confusion, because you see a guide for Fedora and it said dnf install xyz, but dnf doesn’t work. The solution is to add it to your image tree (no) or to create a toolbox with that package (complicated, requires setup, gets complicated if your tool needs access to Wayland for clipboard or something)).

    Bazzite solves this by using brew, which is a package manager built for macOS which has had immutable systems for years. Brew solves most of the issues.

    For me by the time I went immutable it just made more sense to go full declarative with nix, but nix is also a steeper learning curve.



  • Goto is surprisingly readable.

    Loops don’t get labels. Labels are awesome. Sprinkle in some goto so you can use labels.

    In languages like python inside a loop you have if condition: continue. Except continue means don’t continue, you skip to the next iteration without breaking the loop. That’s confusing as heck (and what is else doing on loops Guido???). if condition: goto loop is more honest.

    I also like that goto is “take my stack frame and run that procedure instead”, which is kind of unique and cool in its own way, and impossible to do with most lexical scoping systems. It’s reliable zero cost function calling (if you can make your optimizer happy).

    Everyone loves repeating “goto considered harmful” and “numbering should start at zero”, but nobody critically thinks about those things. Rules are made to be broken.

    ~Oh, and the numbering argument is totally wrong… using one notation to advocate for another is silly. Offset from zero, but index by domain logic!~