InITNEXTbyNick Gard·Apr 9, 2025Browsers need a “some JS” modeUsers need more options than all or none for enabling JavascriptA response icon1A response icon1
InITNEXTbyNick Gard·Nov 16, 2021Fixing Focus for SafariIn 2008, Apple’s Safari team had a problem: web developers had noticed that links, buttons, and several input elements were not matching…A response icon2A response icon2
InUX CollectivebyNick Gard·Jan 27, 2021It’s time we say goodbye to pixel unitsWhy responsive and accessible websites don’t really need ‘em.A response icon16A response icon16
Nick Gard·Jan 4, 2021Why JS needs native memoizationI have a proposal for a new feature for JavaScript: built-in memoization. Let’s make Function.memoize a reality.A response icon1A response icon1
Nick Gard·Dec 30, 2020Accessible Fluid TypographyScreen-relative units, like vw and vh, are not accessible by themselves. Pair them with relative units to respect the user’s preferences.A response icon2A response icon2
Nick Gard·Oct 3, 2019When Should You Do A Rewrite?Everyone wants to rewrite their codebase. The current one has too much cruft. It’s legacy code. Ugh. But when is it cost-effective?
Nick Gard·Sep 6, 2019JavaScript’s Next Evolution: “use stricter”;“use strict”; greatly cleaned up JavaScript, but there are still some pain points to eliminate. I think we’re ready for “use stricter”;
Nick Gard·Jul 29, 2019Magic Numbers in CSSOne of my more common critiques on code reviews of CSS changes is the presence of magic numbers. I’ll see a property being added with a…
InITNEXTbyNick Gard·Jun 19, 2019Why I Don’t Use CSS VariablesCSS variables, officially called Custom Properties, are amazing. I want to use them, but I can’t. Because IE11 doesn’t support them.A response icon2A response icon2
Nick Gard·May 14, 2019Why NaN !== NaNAmong the many seeming oddities of JavaScript is the fact that NaN (Not-a-Number) is not equal to itself. This is a FEATURE of JavaScript.A response icon1A response icon1
