If 1 pt = 0.75 pixels, then there is no meaningful distinction between the measurements. It's a scale factor. It's like advocating for mm over cm. I don't quite understand the point of the article. If he's worried about terminology, then redefine the word pixel as being 4/3 of a pt. Problem solved. Also, either his last sentence is a mistake, or I must have misunderstood the entire article.
I totally agree. As someone who is a programmer, not a designer my reaction to reading this is: "What is this I don't even...." I figured he was going to be advocating moving to a relative system where the rendering engine was made aware of the dpi of the display and vector graphics (or differently sized bitmaps as in the Android ldpi/mdpi/hdpi model) were used where possible, because we very clearly have to start em…
I'm advocating moving to an absolute system. As in an absolute width, measured here, measured there, measured anywhere. This can then be scaled to mimic the appropriate absolute width based on viewing distance and other parameters such as screen real estate.
I know what you're thinking. "But pixels are an absolute measure...". Actually yes, and actually yes. Pixels are an absolute measure in the sense that they state that I want something to be the absolute size of a single pixel but the pixel is arbitrary and now your absolute measure is relative to the actual size of the pixel. As mighty as this sounds, it actually turns out to be not all that useful in design; as screen resolutions vary so will your renderings. This is why CSS pixels are different, they're for all intents an purposes interpreted as 1/96th of an inch. So, great they're absolutely 1/96th of an inch, they're absolute! So why should you stop using them? This paragraph is why you should stop using them. I didn't like writing this paragraph, and I'm gonna guess you didn't like reading it. Pixels are confusing and pixels are * liars. Use points.