I'm sure if Apple keeps innovating and adopting some of the Web standards they'll outcompete other engines. But let's be realistic, they 100% are blocking other engines and not adopting standards in their own because they want that sweet sweet 30% cut when developers can't publish PWAs and are forced into the "app" model.

▲

cosmic_cheese 4 hours ago | parent [-]

WebKit's progress has been significant in recent years, it's just been more focused on things like improving CSS instead of things like an API that tells the developer how many beers the user has in their fridge.

▲

kelthuzad 2 hours ago | parent [-]

You are unwittingly confirming his point. Apple isn't randomly working on random stuff, they know exactly where their bread is buttered - features that have potential of diminishing that butter get skipped, neglected or implemented half-baked.

	▲	cosmic_cheese an hour ago \| parent [-]
		It depends on how you look at it. From my perspective, Google tends to focus on somewhat niche features that will benefit a small slice of web apps. In contrast, the things Apple works on are those that benefit everything from static blog sites to huge commercial web apps. I wish Google were more like Apple in this regard, because the primitives from which everything web is built are still overwhelmingly crude, which results in the half-ton-truck-built-on-a-golf-cart frameworks and apps the web has become famous for. Making the web reasonable to develop for without a dependency tree that looks like a spiral fractal would do way more to make it flourish as a platform than things like access to the GPU and USB devices.