Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Permalink for comment 552431
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
More News »
Sponsored Links



Member since:
2006-02-01
And that is a problem ? IE6 was a problem for two reasons:
1) it was not developed anymore, meaning no progress
2) only available on a single platform
IE6 was all about locked-in, locking users on windows, and locking users on microsoft technologies. All of that is not possible with Webkit. Since it is LGPL, it cannot become proprietary, and, if Apple cannot prevent others to use Webkit on different platform, also Apple cannot stop progress, if Apple decides to stop development of Webkit, no problem, Google and Opera will carry on the work, and it will give them a competitive advantage over Apple. This is the major difference between IE6 and Webkit, one was blocking progress, the other one cannot.
Shame on developers for developing website that works in real life instead of developing website that would work in a theoretical world...
That said, there is still the need for a good specification to make sure that rendering does not get broken across version of webkit. And that is an area where Opera is a very welcomed addition to the webkit world, they have always been the best at respecting the specification.