because none of the proposed functional problems have proven truly significant, the debate has become one of principle. Eric Garside's critique is that you're not SUPPOSED to use !important this way. my one strict rule is to never strictly follow strict rules. i believe a wise programmer understands the reasons for particular rules, follows them when it makes sense, and breaks them when it makes sense.
"never use GOTO" is a guideline meant to prevent spaghetti-code, is one of those strict rules. it's an old debate. i myself have written ridiculously-deep, impenetrable conditional nests and other programming gymnastics to avoid the dreaded goto, resulting in code that was harder to maintain. as steve mcconnell, author of the fantastic programmers bible "code complete", writes (in support of judicious use of GOTO), "If you have your rain boots on, it's not worth walking around the block to avoid a mud puddle." http://www.stevemcconnell.com/ccgoto.htm i have not yet found any chorus of css-authorities warning against ! important.
