9 ms·
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 mode
by crazygringo 5y ago
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 with pixel boundaries which produces sharper letterforms at the cost of distortion of the aesthetic personality of the font, while Mac antialiases more to faithfully maintain the accurate letterforms of a typeface, at the cost of being blurrier.
It's basically the tabs-vs-spaces debate of font rendering. Nobody's "right", it's just personal preference. Fortunately, high-resolution "retina" style displays make the distinction much less important, in the same way that it's entirely irrelevant in high-resolution printing.
- krona 5y agoI always thought the biggest difference was subpixel vs grayscale anti-aliasing. Prior to very high pixel density screens, I hated the Mac/android font rendering, mostly due to the migraines caused by my eyes straining to correct for the seemly out-of-focus text blur.
- deleted 5y ago[deleted]
- garaetjjte 5y ago>I always thought the biggest difference was subpixel vs grayscale anti-aliasing. It's mostly hinting. Windows actually doesn't do subpixel antialiasing in many applications anymore. (such as Start menu or new Settings panel)
- danybittel 5y agoOf course it does.
- formerly_proven 5y agoI don't understand why you write an incorrect comment when checking whether GP is right takes literally seconds in front of a Windows box (open start menu, screenshot, enlarge, clearly not using subpixel AA).
- deleted 5y ago[deleted]
- danybittel 5y agoIt's because that is exactly what I did. And the text in my Start menu has AA? I'd be really surprised if any text doesn't have AA.
- nwallin 5y agoIt'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.
- oneplane 5y agoAt 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 suppose it really depends on the specific user and their user-case to have that matter (or not matter at all).
- ithinkso 5y agoOr in other words - software isn't written to be used, it's written to be sold
- kzrdude 5y agoThis is a good explanation for why open source projects sometimes deliver something more useful - when they are written to be used.
- oneplane 5y agoYep, but it does depend on what you are selling, or what you 'say' you are selling. Within UX you can focus on many things, be it an abundance of choice vs. known defaults, aesthetic vs. utilitarianism, CAPEX vs. OPEX etc.
- gjsman-1000 5y agoWhat if I want my window buttons on the bottom instead of the top? What if I want my taskbar in the middle of the screen instead of the top or bottom? What if I want textboxes to have flashing orange outlines around them? What if I want the close button to be blue instead of red? What if I want the Finder face to be a sad face instead of a smile? Customizability needs to end at some point. Technical details about font rendering is not important to 99+% of users and is only confusing.
- speeder 5y agoOn CRT screens win8 rendering was crazy blurry for me until I installed mactype
- aasasd 5y agoA side-effect of Windows pinning fonts to pixels is that you can't get arbitrary font sizes and scaling. E.g. I had to use “font-size: 82%” in CSS, because at 80% the text looked bad (pinned to the wrong pixel, and possibly became blurry, can't remember for sure). Likewise, zooming in browsers was a mess. This was ten years ago, so dunno if anything has changed.
- graftak 5y agoYou were likely looking for 81.25% which—with the universally accepted default browser font-size of 16px—equates to a whole 13px (16 * 0,8125).
- aasasd 5y agoAfaik 16px only relatively lately became the ‘default size’ on the web. I'm not even sure that ‘css pixels’ were a thing ten years ago. But it's possible.
- graftak 5y agoI’m not exactly sure either but that is around the time I got started with css and I can still recall a lot of these 16px conversion ratios[1], they must have hade some significance. Edit: now that I’m thinking about it, I (used to) use Spotlight for the conversions which was introduced in Mac OS X 10.4, released in 2005. [1] 62.5% for 10px, 87.5% for 14px, etc.
- forrestthewoods 5y ago> Fortunately, high-resolution "retina" style displays make the distinction much less important Ahhhhhhhhhhhhhh. Windows machines are still primarily 1080p. Windows renders font differently that macOS/iOS and is lower resolution. The number of graphics designers that fail to test their font or content on 1080p Windows machines is too damn high!
- hsn915 5y agoI 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.
- ObscureScience 5y agoI don't agree with that. I think it's pretty clearly about preference. On non retina displays, MacOSX really is blurry, and my preference is clear lines, preferbly without antialiasing, an certainly without subpixel AA. I think pre cleartype Windows, Classic MacOS, or X11 with bitmap fonts looked the best, but was not flexible enough for modern requirements.
- p1necone 5y agoI still think bitmap fonts are by far the most readable at smaller sizes on lower dpi displays - you can fit so much more code without having to scroll, and I don't find it any harder to read than large TTF fonts on the same screen. TTF fonts at small sizes on newer ~200+ dpi screens are even better again though. I'd love to try coding on a high res color e-paper screen.
- tssva 5y agoAnd here is proof that it is personal preference. I hate the font rendering on macOS and think Windows is clearly better. I even think the font rendering on modern Linux distributions is superior to that on macOS.
- arsome 5y agoInteresting, 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.
- alkonaut 5y agoYes but unlike Tabs-vs-spaces or vim-vs-emacs, in this case at least ClearType is right and the other one is wrong...
- nsonha 5y agoI always find Windows the worst of the 3 (comparing to either Gnome or Mac), so they must be doing something wrong there. I remember you can tweak it in control panel though? Used MacType back in my window 7 days and I remember being quite happy with it. These days when I tried it out on windows 10/11 it does not seem to improve the experience much, perhaps fails to patch some elements of the UI, I don't care enough to investigate.
- Firehawke 5y agoThis was exactly what irritated me and sent me over to this thread-- there's basically no comparison shots to get an idea of how this should look. For something that's so visual, you really REALLY need to draw the eyes to something that shows why you need to download it.
- sossles 5y agoSame here. The website is bizarrely uninformative. A Windows logo, but it's called MacType with a Mac-style download button, with zero explanation as to what the product actually does. The tagline "the way texts should be" is terrible English and it looks blurry on my screen, so the idea that this is some kind of improved font rendering is undermined.
- Abishek_Muthian 5y agoOn Linux or at least on Gnome Tweaks both hinting and anti aliasing can be adjusted according to the preference and they look excellent. Is that not the case with Windows? On macOS I remember having to explicitly enable font smoothing in Mojave for non retina displays to fix the blurry fonts, But I don't think it did much difference.
- citrin_ru 5y 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 with pixel boundaries which produces sharper letterforms at the cost of distortion of the aesthetic personality of the font Fully agree that it is a personal preference: a slightly distorted shape is something I stop to notice after a day of using the system (I adapt to whatever shape font has unless it is badly distorted like in FreeType with some settings). Blurry fonts on other hand are always look blurry for me. Personal anecdata: I use MacOS daily and FreeBSD every few days, but when once in a while I boot Windows 7 I always pleasantly surprised how nice and sharp windows fonts look; it is especially noticeable if I compare small font sizes across the systems.
- ricardobeat 5y agoYou got it backwards on “I adapt to whatever shape font has” though. The Mac rendering while a little less sharp means letters always have roughly the same shape, as intended by the typeface authors, while the Windows anti-aliasing distorts them unpredictably depending on where and which pixels they fall onto. Two ‘a’s might look slightly different within the same word because they fall into different alignments on the pixel grid. This is what gives it the wonky appearance.