At 18:01 31/12/2000 +0200, Henri Sivonen wrote:
>In article <92ncd2$[EMAIL PROTECTED]>, "Ross Evans" wrote:
>
> > Mozilla could play a part in stopping this from happening, but given the
> > rate of progress, and the emphasis on creating a 'application development
> > framework' rather than what 99% of people want from the project a light
> > weight web browser, this seems unlikely.
>
>I think Mozilla-the-browser has to major problems:
>1) Other Internet apps are tied to the browser
I'd dispute that, that's only true if you want it to be. I only use it as
a browser, I have other clients for other uses, its unlikely I'd want to
run the rest. So I'd say it was overly complicated but not that it
requires other apps to be bound to it. On the other hand there are great
advantages in being able to roll entirely different applications to a
browser but that needs a compliant renderer.
>2) The front end isn't native
If that's really a problem for you then why are you involved at
all? Because this major problem (ie design decision), defines the whole
product. I'll grant you I wasn't entirely ecstatic about losing platform
specific UI as it tends to mean re-bashing wheels all over again, likely
with spokes missing. But it also promises the generation of applications
very cheaply that are to a degree far greater than any other competitive
method highly XP. Put that along with increasing support of CSS2 system
properties and I think its an overall win.
Happy New Year :-)
Simon
--
>Henri Sivonen
>[EMAIL PROTECTED]
>http://www.clinet.fi/~henris/
