Re: SimpleWebKit (was GNUstep Web browser (was Re: WebKit Bounty))

[address@hidden]

> Not only so, but there's the fact that a lot of websites are tested in one, 
> MAYBE two browsers.  If you're not bug-for-bug compatible with Gecko, IE, or 
> WebKit, you're wasting your time.  Period.  Using an existing engine is a 
> force multiplier.  Not using an existing
engine is insanity, unless you have a very restricted set of goals.
 If you want a web browser, your goals are not so limited.  Anybody
who thinks "I'll just implement those handy open specs on w3c.org!" is
on a fool's errand.

Quite offending talk, don't you also think so?

And: where would Linux or GNUstep or Gecko or IE or WebKit be now if
they had followed your recommendations? We would still all use BSD and
Netscape 1.0. Period.

> Go ahead and do it if you want, but it's not suitable for a web browser, 
> especially with a small set of developers.

How do you know before you have done it? Can you predict the future?
And has the pure number of developers ever been an indicator for
project success?

-- hns