Benchmarks are all over the place, but the interesting bit about this one is that this one is really spurred by Google forking the Webkit project, making its own spinoff called “Blink,” which allows it to separate itself from Apple’s Nitro JS processor, which Chrome doesn’t utilize.
Samsung (and others) end up as the odd men out though, as it uses the Apple WebKit Engine, but Chrome’s V8 JS engine. Things could get interesting going forward if these forks… well fork more.
Nice writeup (of a writeup) on how WebKit monoculture (Chrome, Safari, Opera and their mobile counterparts, along with some other lesser used browsers) all having WebKit as their underlying structure.
It turns out that Opera is coming over to the same core that powers Chrome and Safari — WebKit. This is great for web standards, and great for the WebKit project, as the Opera developers will now be contributing to that open source project as well.
Hat tip, Ben. I echo his sentiment. Who knew Opera had 300 million users?
300 Million Users and Move to WebKit
Everyone who’s dabbled at all in CSS is quite familiar with relative, absolute and fixed positioning. It seems though that WebKit is introducing a new one: “sticky.” I’ll be interested to see if this ends up getting wider support and gains any momentum.
Stick Your Landings! Position: Sticky Lands in WebKit
Guess I don’t have this discerning of an eye, but interesting that the webkit-based browsers are “duller.”
Beefing Up Dull Text in WebKit
Meant to post about this before the weekend. I posted a link via Twitter, but I wholeheartedly think the web shouldn’t revolve a single browser (or two based on the same engine). Web standards exist for a reason, and are a goal for the whole web.
Some of the things that Webkit are introducing are great, can be utilized as things that are added to the spec, but until they are part of the spec, they’re not much use to any self-respecting real world web designer or developer.
Web Developers Sound Off on WebKit Prefixes
Nice writeup on efficiency of CSS selectors in your style sheets in WebKit-based browsers (Chrome, Safari, etc.)
CSS Selector Performance has changed! (For the better)
So far, this will only work in WebKit-based web browsers, but it’s cool nonetheless. The only thing that’s kind of weird to me is in the fullscreen demo, there’s no way to transition to the next image without getting out of fullscreen first. I can think of applications where this makes sense, but also can think of more where the nav would be desirable while in fullscreen image viewing.
Fullscreen Image 3D Effect with CSS3 and jQuery
You know all those reflective product-highlighting images that are made to look like they’re on a reflective surface a la Apple? Now, you can create those reflections in your web browser, if your web browser is WebKit based, that is.
Mastering CSS Reflections in Webkit