Interview With the Chief Architect of NGLayout, Rick Gessner
Wednesday October 28th, 1998
Well folks, mozillaZine has another first for you - content you won't find anywhere else on the Net! Today we're offering an extended look inside the Next Generation Layout engine being developed by the Mozilla Project. We have an amazing interview with Rick Gessner, the Chief Architect of NGLayout, about the history of NGLayout and why it truly qualifies as a new paradigm in layout technology. It should also put to rest any doubts as to which company is the true innovator in the browser market.
Click Full Article to start.
#10 Re:Interview With the Chief Architect of NGLayout,
by Aleks <firstname.lastname@example.org>
Friday October 30th, 1998 10:50 AM
You are replying to this message
I don't think anyone can deny that IE4 has faster layout than NN4. That to me is one of the few technical advantages IE has, although it is a very important one. I think if Messenger supported multiple POP3 accounts and NN had as good layout as IE4, then there would be no reason why anyone should choose IE4 over Communicator. The only reason might be ActiveX support, but I'm talking about _good_ reasons of course :)
Microsoft does have an advantage by working only on the Windows platform, but that is not the only reason why IE4 performs as fast as it does. It has been shown that Microsoft refuses to give out certain Windows APIs to their competitors, and in Barksdale's deposition it has been stated specifically that Microsoft delayed giving Netscape Win32 APIs when Netscape refused to collude with them.
Personally I hope that NGLayout will be better than Microsoft's next offering, and it's certainly faster than IE4. So you can see that sometimes, even a cross-platform product doesn't have to be slower than a Windows-only product. Microsoft's weakness is that instead of trying to make the best standard-compliant implementations, they put a lot of their energy into inventing new proprietary specs, which then have to go through an acceptance process and they often get rejected. So by trying to hijack standards and not concentrating on making better open-standard products, they are in a way helping Netscape and other compete in the open standard arena.
Anyone remember Micrsoft Blackbird? That was their proprietary standard that was going to replace HTML, because it was "better". They were supposed to use it on MSN at first and of course try to get all web developers to use it. Same happened with VBScript, and ActiveX. Luckily ActiveX never took off on the web, and hopefully neither will Chrome. The only way Chrome and other proprietary Microsoft technologies can take off is if MS gets 80%+ of the browser market, and that is why it is *WRONG* to use IE and thus help them achieve that goes. When this happens, you will only be able to view all the information on the web using Microsoft Windows...