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?"
If you read TFA (haha!) make sure to scroll down to the comment of Pater Kasting (Chrome dev).
Must admit, although I primarily use Firefox or Chome; I have no problems at all with IE. I don't understand why people would "cheer for its demise". IE9 is a good browser, and I'm all for competition. Less competition in any space is generally bad for users, if things swing too far toward one engine we'll be in the same position we were when IE6 was the "standard" and people ended up only bothering to test on that browser. That causes stagnation.
Code, Hardware, stuff like that.
I still want to see three viable rendering engines competing in the browser world - and that's what we currently have.
I know there are a few people who live and die with Opera, but it didn't have enough market share to make any meaningful difference - its switch to WebKit is irrelevant to most of us.
#DeleteChrome
Frameworks to do simple things may be stupid, but it's just as stupid to write your own code every time too. It's hard to say which one is worse, but I'm going to say it's worse to never use a framework than to always use one unless your time has no value and you always write perfect code.
In my current position, I have definitely had to implement at the very least twice as many Chrome workarounds as IE in the last six months. I was very surprised to see Chrome behaving oddly and Firefox and IE rendering the pages identically, as prior to that time period, I had never seen Chrome and Firefox render a page in a substantially different way.
Most of the issues have revolved around Chrome "over-reacting" to what it perceived as an XSS attack.
According to the author, Opera should spend their time and money to fix old edge-case bugs in WebKit, but he shouldn't have any obligation to contribute patches himself.
Sorry sir, but that's not how open-source development should work. If you're going to spend time rebuilding your own codebase, evaluating whether a ton of old workarounds are still necessary because of missing "half-line fix[es]", you should consider spending some of that time contributing such simple patches upstream to improve the situation. With IE, that was never an option, but it is with WebKit. In an open-source stack, the only workarounds that should be accepted as the regular course of business are ones that are prohibitively difficult to implement in the dependency, or where the patches have been submitted and rejected.
What's most entertaining is the reference to the "tragedy of the commons" in TFA's title. Tragedy of the commons is not something being so commonly used that it's improved in places you don't like. Rather, it's where everybody using the common property thinks that maintenance is someone else's problem. Mr. Methvin, WebKit's maintenance is as much your problem as it is Opera's.
You do not have a moral or legal right to do absolutely anything you want.
I code everything by hand, if it doesn't work in some browser, then that browser's implementation is broken.
You say this like that somehow is a solution.
Pretty good is actually pretty bad.
This isnt a 'WebKit' problem, this is a Mountain Lion + Safari problem. Safari started implementing a lot more things to leverage the GPU in rendering and it did not turn out very graceful.
No, it is not just him. This corruption problem with Safari is a well known problem. It appears that this problem manifests strongly in the macbook retina. There are ongoing discussions about this in many forums, including apple's own:
https://discussions.apple.com/thread/4148522?start=0&tstart=0
As reported by many testers, these problems have NOT been fixed in the soon-to-be-released 10.8.3 update, and they are still present in the Webkit nightly. If you are not experiencing such problems, the most probable reason is that you're using a non-retina display.
If I clone myself, can I call it a thread?
If a girl winks to us, can I call it a race condition?
"WebKit As Broken As Older IE Versions?"
Yes! Because any two things that are not perfect are equally bad. :-|
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
It's inertia. IE6 was a terrible browser. IE7 and 8 were better, but not markedly so. IE9 was a total turnaround for Microsoft, and IE10 is keeping with that trend.
However, the damage is already done. On top of it being a Microsoft product and thus being automatically terrible, dangerous and likely to cause the death of a few Linux whackjobs, its bad reputation in the past has stuck to it like a skunk's stink. Is it deserved? Not anymore, no. But you probably have noticed by now that for all our claims of technology being a fast moving sector, a lot of the people working in it are old men shouting at you to get off their lawn ;)
Opera's shift to WebKit should concern everyone. It's likely a good decision for them, but it consolidates WebKit's position as the dominant rendering engine, and having any dominant engine is bad, as you go from standards directing engines to the dominant engine imposing "standards".
Ironically, it's Firefox which is still doing its job: never the dominating browser, but always a significant enough force to stop any one browser from entirely dominating. Those who think Mozilla's outlasted their welcome should think again.
I have no problems at all with IE. I don't understand why people would "cheer for its demise".
If you don't hate IE, then you haven't been building websites. For years, the standard process for me was to write perfectly valid HTML and CSS that would render the same way in every other browser, and then spend time screwing around with it until it looked correct in IE. It added 10%, easily, to the cost of every project, and I've read of others claiming 30% or more.
Q: What does the "B." in Benoit B. Mandelbrot stand for? A: Benoit B. Mandelbrot
That's a little dishonest. When IE6 was released in 2001 it was quite good. There was also virtually nothing else on the market as AOL let Netscape flounder for five years and the earliest viable releases of Mozilla were still two years away and Firefox another year after that. IE6 also did quite a bit to tighten up the standards compliance at that time, including fixing the box model. Everything leading up to that point was a huge mess of feature-ramming on the parts of both AOL/Netscape and Microsoft while the W3C slowly toddled along.
What Microsoft did that was blatantly stupid was to stagnate IE for five years between 6 and 7, effectively halting the development towards better standards compliance. And while Netscape at least had the excuses of recent acquisitions and bad project management Microsoft did this quite intentionally by all-but-disbanding the IE team entirely.
IE has come a long way since then. IE9 and especially IE10 are very usable browsers in terms of speed and compliance. They're not perfect, but nothing is. What we need above everything else is an accurate measure of compliance. The W3C HTML/CSS Test Suites are the perfect avenue for that, very narrow unit tests of specific rendering functionality. The problem is that it's not as pretty or fancy as some colorful ACID test.
Here's a few reasons to use libraries and frameworks:
1) Development speed.
2) Browser support and testing.
3) Maintenance.
I'll let you figure out how they help in those situations - and there are many other reasons, on top of those.
developers need to stop using "frameworks" and "libraries" to do simple things.
Seriously, this is a really fucking stupid thing to say. Imagine telling a C developer to re-implement printf() for every application (and every platform it will run on) that needs to print a line of output.