Comments on: The WebKit culture & web rendering engine diversity

By: What should we make of Blink, Google’s new rendering engine? | memeburn

What should we make of Blink, Google’s new rendering engine? | memeburn — Fri, 05 Apr 2013 06:56:56 +0000

[...] It means we’re getting a new rendering engine, thus contributing to the needed diversity I talked about in “The WebKit culture & web rendering engine diversity“. [...]

By: Thoughts on Blink, Google’s new rendering engine - Robert's talk

Thoughts on Blink, Google’s new rendering engine - Robert's talk — Thu, 04 Apr 2013 10:48:27 +0000

[...] It means we’re getting a new rendering engine, thus contributing to the needed diversity I talked about in The WebKit culture & web rendering engine diversity. [...]

By: The five features I like most about Opera (and Presto is none of them) « console.error

Wed, 20 Feb 2013 16:44:46 +0000

[...] implications for web development are different, but many others have written about [...]

By: Michael Tsai - Blog - Opera Switches to WebKit

Michael Tsai - Blog - Opera Switches to WebKit — Mon, 18 Feb 2013 01:46:34 +0000

[...] Robert Nyman: [...]

By: WebKit: An Objective View - Robert's talk

WebKit: An Objective View - Robert's talk — Thu, 14 Feb 2013 15:38:42 +0000

[...] This post is co-written with Rob Hawkes, and as a follow-up to The WebKit culture & web rendering engine diversity [...]

By: Ed

Ed — Thu, 14 Feb 2013 09:30:30 +0000

I have yet to find answers, Why did Opera not Open Source their Browsers if they are ditching it?

By: 2013/02/14 Opera?WebKit??????? – ???HTML5?????? | OpenWeb

2013/02/14 Opera?WebKit??????? – ???HTML5?????? | OpenWeb — Thu, 14 Feb 2013 01:10:35 +0000

[...] The WebKit Culture & Web Rendering Engine Diversity [...]

By: Opera to leave Presto, go to Webkit - GrantPalin.com

Opera to leave Presto, go to Webkit - GrantPalin.com — Thu, 14 Feb 2013 00:22:15 +0000

[...] The WebKit Culture & Web Rendering Engine Diversity (Robert Nyman) [...]

By: tom jones

tom jones — Wed, 13 Feb 2013 21:32:38 +0000

Louis-Rémi:
“The software being Free with multiple competitors working on it, I don’t feel like we’re heading toward another IE6.”

except when you look at the dominant platform iOS (which is, coincidentally, at the root of the business reasons behind the Opera switch).

chrome on iOS doesn’t use a different, potentially “better” “chrome webkit”, it can’t use V8 (and even has slower JS than the default browser because of lack of Nitro), and can never have any new web features apple doesn’t like, like WebGL, IndexedDB, WebRTC, etc..

so you say: webkit is open source, even if apple stopped working on it (because it was, say, opposed to their business interests regarding the App Store), google, adobe, opera and others would take over and carry the torch, right?

except there is no (magic) mechanism that would/could ever let them upgrade webkit on a billion iDevices, so IE6-like problems are just as likely on the “major platform of the future” if apple thinks its in their interest.

and that’s bad..

By: Tanny O'Haley

Tanny O'Haley — Wed, 13 Feb 2013 21:17:49 +0000

EB,

Exactly, the button element is a standard form element and the user should automatically be able to tab to it without having to go to advanced preferences. Lack of scroll bars on overflowed elements is a usability nightmare.

By: Opera wechselt die Browserengine « F-LOG-GE

Opera wechselt die Browserengine « F-LOG-GE — Wed, 13 Feb 2013 21:04:12 +0000

[...] The WebKit Culture & Web Rendering Engine Diversity (Robert Nyman) [...]

By: the_dees

the_dees — Wed, 13 Feb 2013 19:40:27 +0000

Unfortunately, WebKit is not great.

Actually, if you keep in mind by what companies the engine’s backed up by (Google, Apple), one can frankly say it sucks (e.g. it’s CSS 2.1 support is way behind IE’s).
Microsoft has learned it’s lessons, Apple and Google still haven’t.

I can only hope that all those Opera developers will improve the engine to be as great as Presto is. Good luck Opera, I’ll miss you.

Anyway, I’ll support Opera in the future, even though my current feelings are still mixed.

By: Regis d'Aubarede

Regis d'Aubarede — Wed, 13 Feb 2013 19:19:52 +0000

This mean a new contributor for WebKit, no ?
And tha is great, yes?

By: EB

EB — Wed, 13 Feb 2013 18:30:53 +0000

Oh, and “Reminds me of the old days of working on IE”. Really? Come off it, there is NO way Safari nor chrome or anywhere near as painful as IE5 and IE6 were…

By: EB

EB — Wed, 13 Feb 2013 18:28:57 +0000

@Tanny O’Hally:
“Safari has problems too, for instance not tabbing to buttons on forms.”

That is a setting in preferences under advanced. If you want it to always tab to every control, you check the box “Press Tab to highlight each item on a webpage” Otherwise it is Option-Tab. If you check it, they reverse (Tab highlights all and option-tab just the entry boxes)

By: Hey Presto… | Andrew Hayward

Hey Presto… | Andrew Hayward — Wed, 13 Feb 2013 17:35:05 +0000

[...] opinions have been given already, many from people within relevant organisations including Google, Mozilla, and Opera. You probably want to start with those — they’re certainly more eloquent [...]

By: Robert Nyman

Robert Nyman — Wed, 13 Feb 2013 15:45:13 +0000

Tanny,

Well, even if it’s one engine that many work on, it comes down to prioritization, what’s deemed important to fix etc. My personal belief is that multiple engines from different backgrounds helps with that.

By: One less browser engine | Beyond the Code

One less browser engine | Beyond the Code — Wed, 13 Feb 2013 15:38:30 +0000

[...] Robert Nyman [...]

By: Tanny O'Haley

Tanny O'Haley — Wed, 13 Feb 2013 15:34:41 +0000

WebKit is the new IE. Many rendering bugs. Chrome doesn’t support hyphens and has many problems with scrolling. Safari has problems too, for instance not tabbing to buttons on forms. Working on web applications for Safari reminds me of the old days IE. I would prefer the competition of multiple rendering engines. With multiple rendering engines there is incentive to make things better.

By: In the News: 2013-02-13 | Klaus' Korner

In the News: 2013-02-13 | Klaus' Korner — Wed, 13 Feb 2013 15:03:41 +0000

[...] Programming News: The WebKit culture & web rendering engine diversity The web. Diversity. Options and competition. Today Opera announced that they’re moving from their own web rendering engine, Presto, to WebKit, and it’s described more technically in Opera’s Developer Relations blog, where it’s made clear they will also use the V8 JavaScript engine. I thought I’d express my thoughts on this – what it means and what I’m afraid developers erroneously will believe it means. While I work for Mozilla, who does the Firefox web browser, these are my opinions on the topic, and I’d have them no matter who I’d work for. Read full story => Robert’s Talk [...]