I'm sorry I don't agree. Using !important should always be a last resort but sometimes it can't be helped. I occasionally come across the unavoidable working on large scale dynamic websites, I ALWAYS try to find an alternative and reconfigure the specificity but sometimes the means justifies the ends, this especially true when the code is being passed onto another developer at some point. Forcing a goose-chase type workaround with specificity can be just as detrimental as using !important.
I also don't believe it shouldn't be taught to beginners. Once they figure out that it exists they will use it thinking it's a natural path of their learning, much like JavaScripts eval() method.
I'm sorry I don't agree. Using !important should always be a last resort but sometimes it can't be helped. I occasionally come across the unavoidable working on large scale dynamic websites, I ALWAYS try to find an alternative and reconfigure the specificity but sometimes the means justifies the ends, this especially true when the code is being passed onto another developer at some point. Forcing a goose-chase type workaround with specificity can be just as detrimental as using !important.
I also don't believe it shouldn't be taught to beginners. Once they figure out that it exists they will use it thinking it's a natural path of their learning, much like JavaScripts eval() method.