IE7 and the use of CSS Hacks
When I first read of Microsoft's call to remove CSS hacks, I wasn't too concerned. As Eric Meyer mentions, if they've fixed the rendering bugs and they've fixed the CSS parsing bugs then the hacks will continue to work on their own.
The point that a lot of people seem to have missed, and what really seemed to be the point of the IEBlog post, is that gray area where Internet Explorer will render something differently than other browsers but still meets the W3C spec. The problem with using parsing bugs to fix rendering differences is that once the parsing bug is fixed, your rendering difference will reappear.
Browsers will naturally have subtle differences in how it renders default behaviour. We should therefore look to CSS styles that, when applied, render consistently across the board. Like the Global White Space Reset. If there are still rendering issues then research to see if it's due to a browser bug and apply a CSS hack only in this circumstance.
In the end, no matter which company comes out with a new browser, the only thing you can do is wait until it's released and deal with it then. No use crying over milk that hasn't been spilled yet.