timber at lava.net
Fri May 26 01:00:17 PDT 2006
I don't mean to white knight, but I don't think Rentzsch was saying
"WebKit sucks, Firefox roolz". I think he was merely pointing out
that there are still problems with Dashcode becoming a full-fledged
I haven't read any of the other blog posts on Dashcode, I don't know
what they're saying. However, I think, in general, it's important to
1) Dashcode isn't even officially released. It's only through a
mistake that we even know about it.
2) Safari, JSCore, WebCore, and WebKit have spent a lot less time as
mature frameworks than their Moz equivalents. There has been a lot of
improvement since WebKit went public, and I think we're going to
continue to see more.
The "pundits" have a valid point: at this stage, JSCore is still
playing catchup with FF. That's a bit of a red herring, though.
What's important is that the WebKit guys are playing the game—unlike
IE, which has gone nowhere. You miss 100% of the shots you don't take.
On May 25, 2006, at 9:22 PM, David D. Kilzer wrote:
> the one in Firefox. Although WebKit's JS engine has not achieved
> feature-parity with Firefox, there are a number of people spending
> their own time documenting bugs, writing test cases, and coding
> fixes for these bugs. And that doesn't even include the Apple
> employees working on the project.
> It's a lot easier to post a blog entry saying that WebKit lacks a
> feature than it is to implement a missing feature or fix a broken
> On May 25, 2006, at 10:50 PM, Colin Barrett wrote:
>> My main question is: Is WebKit's JS worse than FF's, or simply not
>> the same, which could lead to breakage.
>> On May 25, 2006, at 3:04 PM, Abhi Beckert wrote:
>>> I've seen several blog posts recently (eg:
>>> http://rentzsch.com/code/dashcodeForAjaxAppDevelopment) that boldly
>>> state WebKit's "ajax support" is vastly inferior to FireFox. [...]
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev