4 ms·
Honestly it might be a trivial thing to most people but I really do find the way Linux tends to render fonts to just be really telling and ugly, this has genuin
by smt923 8y ago
Honestly it might be a trivial thing to most people but I really do find the way Linux tends to render fonts to just be really telling and ugly, this has genuinely put me off using Linux more for development stuff as it's a big problem with VSCode in my experience
- carbocation 8y agoI use the go font[1] for VSCode on Ubuntu 18.04 and I find it to be pleasant. 1 = https://blog.golang.org/go-fonts https://blog.golang.org/go-fonts
- TheSwordsman 8y agoCan't unsee the terrible letter 'J'.
- Jaruzel 8y agoTook me while to find just the TTFs... Here if anyone else just wants the fonts: https://go.googlesource.com/image/+/master/font/gofont/ttfs https://go.googlesource.com/image/+/master/font/gofont/ttfs / Edit: They don't work with Windows. :(
- clircle 8y agoI find that I go back and forth on this. When 1024 x 768 resolution was standard-ish, I really preferred Linux font rendering. At 1080p, I think I like Windows Clear Type more. At higher resolutions or PPI, it doesn't matter much.
- boomboomsubban 8y agoWhen have you tested it? This kept me off Linux for years, extended use would cause me horrible headaches, but FreeType 2.7 fixed my issues completely. That was released two years ago now, but it's still not on some distros and I've heard GNOME may disable the changes by default.
- mohammedbin 8y agoI'm definitely a Windows fanboy if anything but in general I've found Linux doing font rendering better than Windows. And that's since the last 6 years. Which makes me think maybe it's my settings? If think it's only for Firefox on Windows. Would you have any tips?
- boomboomsubban 8y agoI have a wild guess. Windows changed the default font to Segoe in Vista, which was released eleven years ago, and you are not a fan. I'm guessing six years is a rough guest or you stuck on XP, or dealt with this problem and forgot you did it years later when you reset settings. That said, I searched "Firefox Segoe" before writing this and the top few results were from about six years ago when some naming problem caused Firefox to use the wrong version of Segoe. Worth checking on your own.