#webkit2

"Blink" isn't just a clever reference to rendering and operating speed with Google's new fork, apparently.

I'll just leave this right here.. 

That last bit is what interests me.  They won't be using the experimental flags such as -chrome for us web devs.  Instead, apparently, they are leaving it up to users to enable the experimental features.

Yeah, that makes a LOT of sense (careful, don't blink; you might miss the sarcasm).

What this means for me is that, when there is a reasonable amount of cross-browser support for new standards, such as lovely css3 rendering methods, Chrome won't enable it until they are 100% sure its done.  Until then, its up to users to enable it.

While I'm all about having a solid, well-tested foundation for CSS and HTML standards, and love it when they render consistently across browsers in the proper supported fashion, I'm also sick of waiting for features to reach us in the web dev world.

I myself am just now getting ready to implement HTML5 and CSS3 features into my website, aside from a few gems I already use that are well supported (and, when they don't render, won't break the entire design).  I like things working.

CSS3 is a different beast, as many options I'll be using in my new portfolio are only supported through optional -flags per browser.  This doesn't bother me TOO much, although it does make long-term support difficult for clients, in the case of something changing, or the flags getting removed once support has been finalized in the browser.

With Chrome's userbase reaching far and wide, as well as Opera's decision to switch to Blink, too, I'll have to wait that much longer to start using new rendering options.  If Google can't keep Blink updated with the latest standards, we'll be left with the old chestnut of IE6 vs. the rest of the world..  Using browser headers to determine which version of the site to render.