Useragentman is a front-end developer's blog on cross-browser CSS, JavaScript, HTML5, and accessibility techniques.
HN commenters link its article with an implementation for detecting font smoothing in JavaScript, and cite it on web accessibility.
outside of the company walls as the context for empirical measure:
1. is the web becoming more [accessible](https://abilitynet.org.uk/news-blogs/inaccessible-websites-keep-disabled-people-out-work-abilitynet-tells-government-taskforce http://useragentman.com/wcag-wishlist/)?
2. are the web pages getting [faster](https://www.nngroup.com/articles/the-need-for-speed/) and lighter?
3. is it righting wrongs about existing non-performant [code](https://www.webperf.tips/tip/cached-js-misconceptions/)?
4. is it encouraging [smaller](https://dyf-tfh.github.io/)?
5. is it promoting historical [insights](https://qntm.org/clean)?
6. is it popping [bubbles](https://www.youtube.com/watch?v=Y7YAXUWG820)?
7. is it encouraging the correct interpretations of actual [innovators](https://mamund.site44.com/articles/objects-v-messages/index.html)?
8. is it minimizing or eliminating [traps](https://www.gnu.org/philosophy/javascript-trap.html)? (also see the W3C's Web Sustainability Guideline's on javascript fallbacks)
9. is it avoiding the "[wars](https://tanzu.vmware.com/content/blog/framework-wars-now-all-restaurants-are-taco-bell)"?
10. is it shedding the object-form? https://dreamsongs.com/ObjectsHaveFailedNarrative.html
This article explains and provides an implementation to do that: http://www.useragentman.com/blog/2009/11/29/how-to-detect-font-smoothing-using-javascript/