My modified Antergos Lightdm

seen from Italy
seen from Hong Kong SAR China

seen from Singapore

seen from Malaysia
seen from Israel
seen from Israel
seen from Israel

seen from Israel
seen from China

seen from Malaysia
seen from T1
seen from Yemen

seen from France

seen from United States
seen from United States

seen from Malaysia
seen from China
seen from Spain
seen from Netherlands
seen from Singapore
My modified Antergos Lightdm

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Google forks WebKit. I'm slightly annoyed.
"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.
I hate that. I can code a single version that works well for a variety of platforms; including mobile. I do this because it saves time, which also saves money for clients. If they want a mobile specific version, no problem! I can handle that. Now, though, I may just have to worry about a Chrome-specific version.. And with Chrome's update cycle, I have to wait and hope something doesn't break with each update, hoping I don't Blink and miss it.
WebKit2's type renderer is hugely improved. (No need to use -webkit-font-smoothing: antialiased; ever again!)
Dustin Curtis
Should a crash or hang during browsing occurs, that window or tab is singularly affected. The rest of the application operates regularly, as opposed to the entire app becoming unresponsive. Based on the impressions of the developers, the new Safari does indeed run a lot smoother.
MacApper reviews WebKit2 built into Mac OS X Lion
- Safari in OS Lion uses WebKit 2, that means that it also will have split processes just like Google Chrome. So if a webpage crashes (usually because of Flash :) ), it doesn't crash all the other pages that is open at the same time. Only that page goes down.

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Unfortunately, it appears it's gained something else from iOS: WebKit2 is a private framework.