Well, I appear to be the only person that likes Nanum Gothic Coding. (Though I typically use Input Mono - not present in this site's set of fonts.)
The semifinals for me with ligatures enabled were Inconsolata vs Cousine, and Nanum Gothic Coding vs Xanh Mono. With ligatures disabled: Xanh Mono vs Nanum Gothic Coding, and Share Tech Mono vs Roboto Mono.
It'd be nice if you could click the various fonts in play at the end, to see them again and compare them against one another. (Regarding comparing images against one another: https://news.ycombinator.com/item?id=46954055) I had specific metrics that I was going for, but sometimes it was marginal.
Yeah. I don't get it. If you've got a 3840x2160 display, intended use on macOS as a 1920x1080@2x display, what is the advantage of using a 7680x4320 buffer? Everything is drawn at twice the width and height - and then gets scaled down to half the width and height. Is there actually a good reason to do this?
(I use my M4 Mac with 4K displays, and 5120x2880 (2560x1440@2x) buffers. That sort of thing does work, though if you sit closer than I do then you can see the non-integer scaling. Last time I tried a 3840x2160 buffer (1920x1080@2x), that worked. I am still on macOS Sequoia though.)
> what is the advantage of using a 7680x4320 buffer? Everything is drawn at twice the width and height - and then gets scaled down to half the width and height. Is there actually a good reason to do this?
Text rendering looks noticeably better rendered at 2x and scaled down. Apple's 1x font antialiasing is not ideal.
Especially in Catalyst/SwiftUI apps that often don't bother to align drawing to round points, Apple's HiDPI downscaling has some magic in it that their regular text rendering doesn't.
Yes but Apple got to drop subpixel anti-aliasing support because this workaround is "good enough" for all of their built-in displays and overpriced mediocre external ones, so we all get to suffer having to render 4x the pixels than we need.
I have a number of AutoHotKey/Hammerspoon numpad shortcuts for arranging windows.
In Visual Studio, on the suggestion of a colleague at my first job, I use Numpad + for copy, Numpad - for cut, and Numpad * for paste. (I've never managed to train my hand eye coordination to use these in any other program. Which is a bit of a shame, because they're actually pretty useful. Whichever side you mouse on, you can find some way of hitting them without much effort.)
The numpad also comes in handy sometimes for typing numbers.
Another option might be that Nth pass LLM output is not as good as (N+5 months)th pass LLM output. At some point before the amount of effort involved reaches that required to do it oneself, the output will reach an acceptable quality level... or so you'd hope, if any of this business is to make any sense.
This leapt out at me as well. Given the quote "some evenings", I'd put some money on him actually doing this near enough every day. And given the man was still doing this approaching 50, I'd put a bit more money on him having been doing this for, like, 25+ years.
If you want to maximize the chances of your weed habit causing you problems, this is exactly the sort of weed habit you should develop.
Hm, that's a good point. I totally did not think of that as a possibility. But what are the chances? I mean, it's just a cute little pit bull we're talking about here! It's not as if it's even a big dog, like a golden retriever, or a nice friendly alsatian.
The semifinals for me with ligatures enabled were Inconsolata vs Cousine, and Nanum Gothic Coding vs Xanh Mono. With ligatures disabled: Xanh Mono vs Nanum Gothic Coding, and Share Tech Mono vs Roboto Mono.
It'd be nice if you could click the various fonts in play at the end, to see them again and compare them against one another. (Regarding comparing images against one another: https://news.ycombinator.com/item?id=46954055) I had specific metrics that I was going for, but sometimes it was marginal.
reply