There is no greater failure than showing a white screen. If an application can't run in a given environment ("old" browsers) telling users might not make them upgrade right away. But compared to a blank page they'll actually know what's going on. Here's a (debatable) method to achieve that.Continue reading "Dialog for Unsupported Browsers"
KISS: Keep It Simple (and) Stupid - Writing code for humans. This post explains why I believe using constructs like
~"a".indexOf("b") is a bad practice.
One of the first performance optimization tricks you learn is setting a far-future cache expiration date. This prevents browsers from repeatedly fetching, even revalidating, static resources. The downside of this approach to reducing network overhead is that you need to change the resources' URLs in order to have a browser re-download it. This post covers the problems encountered when using
<base> to achieve exactly that.
I just found out that a high-profile web application was using one of my open source libraries. This post reflects on what led there and what happened next…Continue reading "The Honors Of Open Source"
Firefox - unlike Chrome - allows any web application to register any keyboard shortcuts (y'know the infamous CTRL + C). This might be a problem for users relying on keyboard navigation or even just general keyboard controls. This post shows a way prevent websites from capturing and muting essential commands such as CTRL + W (to close a tab).Continue reading "Reclaim Your Keyboard Shortcuts in Firefox"