Let’s fix font size
&gt; Specify it in pixels<p>No thank you.<p>I regularly wonder if it might not be better for the web if we got rid of pixels as a unit entirely. We can&#x27;t realistically do that for a lot of reasons, and there are legitimate reasons to use pixels <i>sometimes</i>, but resolution independent font-size and container sizing should be the default. If you are using pixels on the web for font sizes, consider this a public intervention that you need to stop.<p>The fact that `em` units are not related to physical size attributes <i>is intended</i>. We don&#x27;t want them to be related to physical size -- what `2em` is saying is that you want a piece of text to be twice as large as the &quot;default&quot; size of the specific font on the platform&#x2F;device. That is a superior way to think about text size, because as a user I don&#x27;t want you to try and figure out what the pixel density or screen ratio or resolution of my device is.<p>Size your fonts with `em` and `rem` units, and size your containers based on the number of characters you want to fit in each line. Don&#x27;t use pixels. It doesn&#x27;t matter if your fonts are bigger on Mac or Windows. It is intentional that platforms can size their fonts differently, and your interface designs should take that into account.<p>If anything, native platforms should be moving more in this direction, they should not be moving away from it. There was a period where you could decide to only care about responsive design on the web, but increasingly you should be thinking about responsive design on native platforms too. And resolution-independent font-sizes based on the user&#x2F;platform are part of that process.<p><i>EDIT: Yes, I&#x27;m aware that pixels on the web are not necessarily 1:1 ratios with physical pixels on a screen. That doesn&#x27;t change anything, pixels are still bad to use on the web. Tying font size to resolution, whether that&#x27;s browser window resolution or physical resolution, is still equally problematic. And it certainly doesn&#x27;t mean that we should move in the opposite direction on native devices -- the web&#x27;s pixels are the way they are because the alternative, being tied to literal physical pixels, would be even worse.</i>