Setting the line-height unitlessly seems to have caused issues for me in Chrome. When font-size is set to something like 14px (which becomes 0.875em) and line-height is set to 24px (which becomes 1.71), Chrome incorrectly renders the line-height as 22px instead of 24px. The fix was to set the line-height in em's instead of unitlessly. So, line 18 would read:

line-height: ($inuit-base-line-height / $inuit-base-font-size) * 1em; /* [1] */

Thoughts on this approach? Is there a reason to use unitless measurements over em's?

https://github.com/inuitcss/base.page/blob/master/_base.page.scss#L16

Fonts on OSX will look more consistent with other systems that do not render text using sub-pixel anti-aliasing.

Can you provide examples of such systems? For me (non-retina macbook air) Finder and all the other stuff actually have the subpixel antialiasing.

And I just can't read (my eyes bleed, all that stuff) the text on sites without subpixel antialiasing, so every such time I need to go and disable it for each site in dev tools.

Without subpixel antialiasing most fonts become too thin to read, especially on small sizes.

An example from css guidelines as rendered on my screen:

The same, but with proper subpixel antialiasing:

And the final example, with the user styles I applied so I can finally read the thing (plus two zoom levels and subpixel aa):

Actually, if you'd sample the colors from the non-subpixel antialiased text, you'll get mostly the values like #6C6C6C which do not pass AAA WCAG 2.0 for small text:

While subpixel antialiasing is increasing the overall contrast, so it starts to fit the WCAG. And on larger font-sizes it becomes even better.

So, a suggestion: either use really larger font-size, or bring back the subpixel anti-alialiasing. Or do both: in most cases it is better to give people larger font size than the smaller one, especially if you're using serif font.