News about design templates
27.10.2005 - CSS Patches
<p>The term "hack" implies that a legitimate solution to the problem exists. Yet, in order to save time, or perhaps due to lack of knowledge, a sloppy fix is applied to <em>just get the job done</em>. "Let's hack at it, 'till it works". But is this the case in terms of <em><abbr title="Cascading Style Sheets">CSS</abbr></em> hacks? Sure, we call them "hacks", when in reality they're really <strong>patches</strong>. Patches that fix known, documented problems in certain browsers.</p>
<p>I know it's really just a term, but the problem is this: by using "hack" to describe often necessary code, a negative connotation can be attached, even if what we're really doing is compensating for a browser's shortcomings. When you hear someone say: "I avoid all hacks", you've witnessed this negative connotation. Heck, we'd all love to avoid hacks -- but we're also realistic, living in the real world, and designing in 2005.</p>
<p>Now think about the term "patch". It brings to mind, <em>mending</em> something that's broken. It's rip or tear is clearly visible -- we know it's broken, and we know what we need to do to make it look better. We're not cutting corners, we're applying a fix.</p>
<p>Perhaps from now on, I'll refer to fixes for gems like the double float margin bug, or the three-pixel text jog as, well... <em>patches</em>.</p>
SimpleBits
Hand-crafted web sites, pixels and text by Dan Cederholm.
|
|
Classifieds
(
Latest comments: