"it's an ugly hack" --people who take pride in the purity of their code might take offense at a solution which is based on expediency, rather than programming dexterity. this debate seems partly to be about programming pride vs. expediency. i wish i had the resources to hire one of you gurus, but i have to wear all hats. to me, an example of an ugly hack is hard- coding values where constants should be used, or applying patch upon patch rather than fixing the whole system.
"has so many potential problems" --such as? every potential issue mentioned in this thread is the rare exception. no one has yet presented a serious or probable problem from !important. and in the rare cases where any of the potential problems occur, then you get to apply your expert programming skills. and of course some programmers, like some auto-mechanics or doctors, who get paid more for doing more work, love to find more problems requiring their expert skills to solve. i prefer finding solutions to prevent more work. if i could hire one of you gurus.... i would hire the ones who find more efficient solutions, rather than more reasons to show off their skills.
