The debate about hacking is mostly about hacking IE lte 7. We have
sufficient methods to hack IE, though. Because of its market share, we
have the knowledge about the bugs, the filtering methods and the
workarounds for IE.
I don't think we need filtering techniques for current "compliant"
engines like Gecko, WebKit, Opera, and probably IE8. I know they have
their bugs too, but for most everyday coding problems, there are
interoperable methods available. The differences that these browsers
show are the difficulties in interpreting a specification that is still
fine-tuning on edge-cases.
Any static filtering method for these browsers under active development
would fail sooner or later, so any hack could suddenly become the
problem it should initially solve.
And other filtering methods, on the engine's version level or the spec's
version level, would quickly surpass the abilities of web authors in
following the latest discussions on the specification, to decide whether
a browser is right or wrong.
A layout should tolerate imprecision by the browser, as it should
tolerate user settings and needs that differ from the author's settings
and needs. The latter is the bigger problem.
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/