A Reader Calls On MS To Adopt Mozilla's Rendering Engine

Tuesday September 14th, 1999

Dave Usher of Tiny Communications, a new free-access Internet service in the UK, writes, "Inspired by the recent discussions on MozillaZine I've written an open letter advocating that Microsoft adopt the NGlayout (Gecko) code for their IE rendering engine."

An interesting idea, IMO, which would preserve standards compliance on all platforms while allowing browser makers to compete in the user-interface arena. Instead of putting out competing (and incompatible) rendering engines, why not rally around a single rendering engine which could help guarantee standards compliance by virtue of its Open Source nature and cross-platform architecture?

#25 Why would this help Microsoft?

by Anon

Wednesday September 15th, 1999 10:20 PM

You are replying to this message

Microsoft's rendering engine on Win32 is amazingly sophisticated for a Microsoft product. It supports CSS pretty much completely-down to specifying the font, color, border, and background of form input boxes! It can also do neat things like layer transitions, and you can even rotate layers. Sure, Mozilla might be able to do that when it is released, but that will be at least a few months away. IE is also quite speedy, and it also allows HTML "Applications" to act as normal Windows programs. Oh yes, IE hasn't been based on Mosaic/Spyglass since version 3. It will be interesting to see whether Mozilla can beat IE.

Mozilla's real strength is in its platform-independence-it runs on dozens of platforms, while IE only works (usefully) on one. After all, if your web page only works on one platform, why not just make a proprietary program? Mozilla works equally well on many platforms, s creating Internet applications with DHTML will actually be useful.

Although Mozilla is already far ahead in platform support, it is up for stiff competition against IE's Win32 rendering engine.