If you want to use this today, you'll still need to sniff for it and call setTimeout if it's not available. So unless those 10ms are really important to what you're doing, this will just cost you more work.
That's the problem with cool new browser features. It just takes forever before they trickle down to enough of your users that it makes sense to use them.
Sometimes it's worth the wait. I can remember thinking all of the above about xmlHttpRequest and how lame it was that I'd still need to switch on it and have Netscape continue to use IFrames to do asynch communication back when IE5 came out.
If you want to use this today, you'll still need to sniff for it and call setTimeout if it's not available. So unless those 10ms are really important to what you're doing, this will just cost you more work.
That's the problem with cool new browser features. It just takes forever before they trickle down to enough of your users that it makes sense to use them.
Sometimes it's worth the wait. I can remember thinking all of the above about xmlHttpRequest and how lame it was that I'd still need to switch on it and have Netscape continue to use IFrames to do asynch communication back when IE5 came out.