the-pellmeister

I’m still rocking my OG first gen MX Master today, 11+ years and counting of daily backpack tossing, having survived 3 MacBooks and at least 7 chargers. My only secret? I bought a $10 padded case for it on Amazon the very first day I had the mouse, and zip it in there every time before it goes in my backpack.

Everything works as new, the only thing that broke is the plastic covering the gesture button.

Maybe not the most popular answer, but... because JIT?

OpenCode Go is hard to beat, $10/mo ($5 first month) for up to $60 worth of tokens if used regularly. And no, you don't need to use opencode, they allow any software to use it.

> ... my main con­cern is ty­pog­ra­phy that faces other hu­man be­ings. So if you’re prepar­ing your code for oth­ers to read—whether on screen or on pa­per—skip the lig­a­tures.

With all due respect, am I the only one expecting a strong argument for why ligatures on my own personal machine's terminal emulator should go?

I think "code for others to read" having to be free of ligatures was never in dispute at all. Unfortunately, the most significant reason isn't even mentioned: people's lack of awareness of the existence of programmer font ligatures. In clear terms: a confusion between != and ≠ does NOT exist for people who don't know of the existence of ligatures: they'll straight up believe they're looking at a ≠. (* if not slightly put off by the spacing around the character).

The one thing I did take away from this, is that people using Polacode/CodeSnap and the likes, should probably be aware to disable ligatures before exporting their pictures.

Works wonders!