Live data from Hacker News

MacType: Better Font Rendering for Windows

github.com

61–70 of 130 posts

Re: MacType: Better Font Rendering for Windows

#61
post #18

Earlier quoted context omitted.

It's wild to me that on both Windows and OSX that something that is obviously just personal preference is baked into the operating system, with no method for changing it. It's on the same level as having an operating system that didn't let you change your desktop background.

Optionality is one of those things that product managers hate right now, so the likelihood of that appearing if it hasn't already are slim That said, Windows has highly configurable font hinting/rendering so I'm perplexed as to why this project is a thing

It's configurable but you still can't configure it to anywhere near macOS's rendering - you can turn down hinting from 11 to like 9.5.

Re: MacType: Better Font Rendering for Windows

#63

Earlier quoted context omitted.

At the same time, everything could be reconfigured at will, but if you can't provider a consistent UX, that wouldn't help a whole lot with sales and customer binding. How much you can, or can't modify as an end-user probably relates to the HIG and general usability and transferability as well. In some ways, there have been cases where you cannot change the background of things, or at least not in an obvious way. I su…

Or in other words - software isn't written to be used, it's written to be sold

This is a good explanation for why open source projects sometimes deliver something more useful - when they are written to be used.

Re: MacType: Better Font Rendering for Windows

#64
post #54

It's bizarre that neither the README nor the associated minimal site explains what it does in detail, with screenshots or anything. I'm assuming this is a modern version of GDI++, which a decade ago brought Mac-style font rendering to Windows, but stopped being maintained a while ago. For people who aren't aware of the difference, it's essentially that Windows uses heavy font hinting to try to align character strokes…

I never understood _why_ but text rendering on windows has always looked like garbage to me. It was obviously not the screen resolution or anything, because you can run a linux vm (say, on virtualbox) and the text rendering inside the VM will look much better than the text in windows. > Nobody's "right", it's just personal preference. I don't think that's true. macos is clearly better.

I'm pretty sure since Windows 8 Microsoft has focused on making font rendering look very good on high DPI displays at the cost of making them look poor on more traditional low DPI displays. Windows font rendering looks really good on 4K monitors and laptops with high res screens. Not so much on your typical 1080p-fare.

Re: MacType: Better Font Rendering for Windows

#65

I had listened to an interview with the original cleartype author on a podcast almost a decade ago now. IIRC He said that when Apple got the cleartype patent (due to the Apple/Microsoft cross patent agreement that happened in the late 90s), they kinda messed up the implementation of cleartype and Windows actually implements it correctly and Mac OS X (now Mac OS) doesn't. So I find this somewhat amusing.

You might be thinking of the interview with the late Bill Hill (2011), co-creator of ClearType : https://thisdeveloperslife.com/post/2-0-5-typo

Re: MacType: Better Font Rendering for Windows

#66
post #18

Earlier quoted context omitted.

It's wild to me that on both Windows and OSX that something that is obviously just personal preference is baked into the operating system, with no method for changing it. It's on the same level as having an operating system that didn't let you change your desktop background.

As soon as you realize that changing rasterization strategies alters the bounding box of character textures, and that a lot of UI positions are hardcoded, it makes sense.

Hardcoding UI positions is one of those "you're doing it wrong" sorts of things. At my day job, both the UX/UI folks and the localization folks would have a conniption if I built something with hardcoded UI positions/sizes, or that broke if the size of a string changed. As soon as you have a user with a hidpi display your application is going to look like garbage. As soon as you want to try to support non-English languages all your hardcoded UI work goes out the window.

Re: MacType: Better Font Rendering for Windows

#67
post #40
post #9

I just switched from Windows to a Mac, and I immediately found that the colors and contrast and the clarity of images and text on the same monitor I connect my laptop too improved. I wasn't sure if it was just in my head, but something about the rendering in Mac seems better to me. I don't know if they have better calibration for colors and contrast, better anti-aliasing, etc., but I seem to see the screen much bette…

Another possibility is that macOS actually does proper color management throughout the entire OS - the Windows shell/desktop is simply not color managed and it's especially irritating when you have a wide color gamut monitor.

Another of the staggering deficiencies for windows. Right next to audio management.

Because audio drivers and colour management aren't important ofc....

Re: MacType: Better Font Rendering for Windows

#68
post #64
post #54

Earlier quoted context omitted.

I never understood _why_ but text rendering on windows has always looked like garbage to me. It was obviously not the screen resolution or anything, because you can run a linux vm (say, on virtualbox) and the text rendering inside the VM will look much better than the text in windows. > Nobody's "right", it's just personal preference. I don't think that's true. macos is clearly better.

I'm pretty sure since Windows 8 Microsoft has focused on making font rendering look very good on high DPI displays at the cost of making them look poor on more traditional low DPI displays. Windows font rendering looks really good on 4K monitors and laptops with high res screens. Not so much on your typical 1080p-fare.

Similar situation in macOS. Sub-pixel anti aliasing was removed in 10.14/Mojave.

Re: MacType: Better Font Rendering for Windows

#69
post #59
post #54

Earlier quoted context omitted.

I never understood _why_ but text rendering on windows has always looked like garbage to me. It was obviously not the screen resolution or anything, because you can run a linux vm (say, on virtualbox) and the text rendering inside the VM will look much better than the text in windows. > Nobody's "right", it's just personal preference. I don't think that's true. macos is clearly better.

Interesting, I personally far prefer the Windows one on 100 DPI displays at least. The blurriness is quite noticeable on OS X and certain Windows applications that attempted to use this style of font rendering. Sure, it's great on higher DPI screens, but then it makes even less of a difference whichever one you use. I'd say Microsoft made the right call here.

I actually agree. MS went for readability on standard screens for ages, MacOS went for staying true to the typeface's design and printed look, which was laudable, but IMO a mistake on screens before the dawn of high-DPI.

Re: MacType: Better Font Rendering for Windows

#70
post #18

It's bizarre that neither the README nor the associated minimal site explains what it does in detail, with screenshots or anything. I'm assuming this is a modern version of GDI++, which a decade ago brought Mac-style font rendering to Windows, but stopped being maintained a while ago. For people who aren't aware of the difference, it's essentially that Windows uses heavy font hinting to try to align character strokes…

It's wild to me that on both Windows and OSX that something that is obviously just personal preference is baked into the operating system, with no method for changing it. It's on the same level as having an operating system that didn't let you change your desktop background.

MacOS > System Preferences> General > Untick 'use font smoothing when available'
Post reply on HN