If you want to get technical: Firefox, Safari, and Chrome have 0 support for the HTML5 standard, considering HTML5 isn't official yet. But they still work toward meeting proposed standard.
Competition is good. If IE9 supports border-radius, and that pushes FF and others to support border-radius without the vendor tag, might that be a good thing?
Only if border-radius doesn't change it's semantics; say the standard switches from radii to area. Or perhaps they add some semantics for negative lengths.
If anything like that happens, then we now have two border-radiuses: Microsoft's and everyone-elses.
I think that with border-radii this isn't likely, but for whatever is still under debate, we could still be looking at this sort of thing.
Getting a little to anal? =)
Okay, before someone jumps on me and thinks I'm being serious, yes, I agree with you. It's 'dangerous,' but at some point, someone needs to say "Damnit! Let's make this work!" After all, you don't see anyone saying we should use vendor tags for HTML5 markup, even though HTML5 isn't complete, and can, and still does, change.
The great thing about standards is that there are so many to choose from. - Someone else, some other time.
http://www.w3.org/Consortium/Process/Process-19991111/tr.htm...
"A Candidate Recommendation has received significant review from its immediate technical community (resulting from the Last Call). Advancement of a document to Candidate Recommendation is an explicit call to those outside of the related Working Groups or the W3C itself for implementation and technical feedback."