The WebKit team just approaches things from a different angle than the Chrome team does. Google/Chrome jump on the new shiny features bandwagon right away to keep the favor of web devs where the WebKit team waits until they know they can implement new features in a way that doesn’t balloon resource consumption and prioritizes end users over developers.

There’s little need for most web apps to be riding up against the edge of standards anyway because 9 times out of 10 they’re bog standard CRUD apps that’ve been trivial to build since the heyday of Ruby on Rails.