You’re reading Register Spill, my weekly newsletter in which I share thoughts I can’t keep in my head. Yesterday, Mitchell wrote about a bug and its fix in his Ghostty Devlog 002. On displays with a DPI that couldn’t be clearly divided by 72, fonts would end up being blurry. Yes, it’s gnarly. I helped find the bug, but reading Mitchell’s analysis made me realise again: in order to truly fix a bug, one must truly know the bug.
Great post. This is even more real when working with legacy code on an environment constrained by management pressure. In those situations, it's often hard to justify major investments in fixes when just a few lines can make the problem seem to go away. Any tips for this kind of situation?
Great post. This is even more real when working with legacy code on an environment constrained by management pressure. In those situations, it's often hard to justify major investments in fixes when just a few lines can make the problem seem to go away. Any tips for this kind of situation?