News for hackers. Stuff that matters.
Re:Blink: A rendering engine for the Chromium project by oellegaard on Wednesday April 03, 2013 @05:27PM (#5489242)
I know it might be an unpopular comment, but I really don't like this. I had hoped every browser would eventually use the webkit rendering engine. I have a hard time feeling sorry for those engineers that have to maintain compatibility, when I think of the many frontend engineers that now have to test a different rendering engine :(
Re:Blink: A rendering engine for the Chromium project by TazeTSchnitzel on Wednesday April 03, 2013 @05:31PM (#5489264)
Rendering engine monoculture isn't a good thing though. If a single rendering engine dominates, then there is less reason to write standards-compliant code - after all, everyone uses WebKit, right?
Re:Blink: A rendering engine for the Chromium project by jmesserly on Wednesday April 03, 2013 @05:46PM (#5489384)
Yeah. It would be the same problem that WebSQL had: http://www.w3.org/TR/webdatabase/

As much as I was sad to see it go, I sympathize with their problem. If you just have a single C/C++ implementation with no spec, it's a lot harder to know, as a user/web developer, what the correct behavior is and what you can rely on.

Re:Blink: A rendering engine for the Chromium project by TazeTSchnitzel on Wednesday April 03, 2013 @05:50PM (#5489421)
Indeed.

It's a shame WebSQL died, though, since I would have loved to have had SQLite in the browser. Maybe the solution would have been to specify a similar, new, SQL database for the web? I would have liked that more than IndexedDB.

Re:Blink: A rendering engine for the Chromium project by dragonwriter on Wednesday April 03, 2013 @07:03PM (#5489891)
> Maybe the solution would have been to specify a similar, new, SQL database for the web?

That would certainly have been a solution, but I think one of the reasons WebSQL went with "use SQLite" as a shortcut was that it was a lot easier. If you specify a reasonably-implementable subset of SQL, you are stuck with that, and you can't piggyback on SQLite maintenance.

I think the decision to abandon WebSQL for IndexedDB rather than expand the spec into something where independent implementations were feasible was probably based on the cost/benefit perceived with having to maintain a separate, browser-specific RDBMS implementation.

Re:Blink: A rendering engine for the Chromium project by ConstantineXVI on Wednesday April 03, 2013 @06:12PM (#5489565)
Why not a JS implementation of a SQL database?
Re:Blink: A rendering engine for the Chromium project by natem345 on Wednesday April 03, 2013 @05:36PM (#5489305)
Just like everyone used IE6 back in the day!
Re:Blink: A rendering engine for the Chromium project by TazeTSchnitzel on Wednesday April 03, 2013 @05:40PM (#5489339)
Yeah, it was wonderful! The alternate browsers just accepted the standards dictated by the dominant browser, and that didn't cause any problems at all!

/s

Re:Blink: A rendering engine for the Chromium project by rictic on Wednesday April 03, 2013 @05:47PM (#5489391)
I'll say from personal experience on two recent projects: if you're only testing in one webkit browser and not hitting the others there's a good chance that you're missing a couple of bugs. There are a ton of different ways to build webkit, Chrome and Safari were never identical enough to ignore. Fortunately, after developing in Chrome it took about as much effort to support Firefox as it did to support Safari, which is to say about half an hour.
Re:Blink: A rendering engine for the Chromium project by mikewest on Wednesday April 03, 2013 @05:54PM (#5489452)
Paul Irish has a great article outlining the technical background of this sort of inter-WebKit diversity: http://paulirish.com/2013/webkit-for-developers/
Re:Blink: A rendering engine for the Chromium project by macspoofing on Thursday April 04, 2013 @02:42AM (#5491341)
>I had hoped every browser would eventually use the webkit rendering engine.

WebKit is not a standard. Writing WebKit code, isn't the same as writing standards-based code. We lived through the ie days, why go back to those?