Slashdot Mirror
WebKit As Broken As Older IE Versions?
An anonymous reader writes "It's not everyday that we get to hear about the potential downsides of using WebKit, but that's just what has happened as Dave Methvin, president of the jQuery foundation and a member of the core programming team that builds the widely used Web programming tool, lamented in a blog post yesterday. While most are happy to cheer for IE's demise, perhaps having three main browser engines is still a good thing. For those that work in the space, does the story ring true? Are we perhaps swearing at the wrong browser when implementing 'workarounds' for Firefox or IE?"
Their drivers are written by 12 year olds, i sware.
Something looks like something was written by a 12 year old.
Mozilla's staying power doesn't surprise me. Firefox is my browser of choice for one reason: add-ons.
Everyone has tried to make their browser support add-ons, and almost everyone has failed.
Firefox has a healthy and useful add-on library. It's very well supported, both by Mozilla and by the community.
IE has an add-on library. But most of the add-ons are for-pay, and I'm just not going to pay for a browser add-on. The free ones are crippleware, shoddy, or both.
Chrome and Safari have... unauthorized patches? At least that was the last time I checked either of them. There might be some "support", but make no mistake: Google doesn't want you to have AdBlock. And Apple doesn't want you to have anything that sets off their NIH alarm.
As for the rest, I haven't bothered with an alternative browser in years. Firefox is open enough, configurable enough, and extendable enough to meet all of my needs. When it becomes troublesome and has true alternatives that aren't, then I'll look for another browser.