Linked by Thom Holwerda on Wed 3rd Apr 2013 22:27 UTC
Google It's apparently browser engine day today. After Mozilla and Samsung announcing Servo, Google has just announced it's forking WebKit into Blink. Like WebKit, Blink will be open source, and it will also be used by other browser makers - most prominently, Opera has already announced it's not using WebKit, but Blink. Update: Courtesy of MacRumors, this graph illustrates how just how much Google contributed to WebKit. Much more than I thought. Also, Chrome developer Alex Russell: "To make a better platform faster, you must be able to iterate faster. Steps away from that are steps away from a better platform. Today's WebKit defeats that imperative in ways large and small. It's not anybody's fault, but it does need to change. And changing it will allow us to iterate faster, working through the annealing process that takes a good idea from drawing board to API to refined feature."
Thread beginning with comment 557594
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: iOS
by majipoor on Thu 4th Apr 2013 12:28 UTC in reply to "iOS"
majipoor
Member since:
2009-01-22

"... and Apple didn't seem all that committed to development of webtechnologies anymore."

Can you elaborate a little bit?

"So does this mean iOS is gonna be left behind more than it is already ?"

Can you elaborate a little bit?

Seriously, the amount of commonplaces one can read nowadays concerning Apple or iOS without any argumentation is amazing.

Edited 2013-04-04 12:32 UTC

Reply Parent Score: 1

RE[2]: iOS
by Lennie on Thu 4th Apr 2013 23:19 in reply to "RE: iOS"
Lennie Member since:
2007-09-22

Well, for starters they ones said their platform would be great for HTML5-apps, now they have the most restricted environment of any platform to run HTML5 apps on. And they don't allow any other browser engines on their platform.

They have no participation in the newest developments like the development of WebRTC or the HTML5-specs.

They have an editor at W3C with a Microsoft editor, but the HTML5-specs aren't really being developed at the W3C. Most of the text comes from the WHATWG.

That gives me the idea of less interest.

I could be wrong of course.

Reply Parent Score: 3