Linked by Thom Holwerda on Mon 5th Sep 2005 13:38 UTC, submitted by Erik Harrison

Permalink for comment 27689
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-06
True to a certain extent, but it isn't about integration, it is about expandability - everything has a plugin interface; there is no need to have the functionality loaded all the time; load it when required, and when the function is no longer required, unload the plugin.
The key to saving memory is re-using components; create a tool kit of components and re-use them again and again; don't have a different rendering engine for each application, re-use the same engine again and again.
That is where Mozilla came unstuck, they tried to do everything when what they should have done, was simply create a core; rendering engine, JS Support etc. then provide interfaces where by people can embed the core into applications - without the need to carry around the XUL bloat, which quite frankly, is a waste of time and has yet to be proven, outside of Mozilla, as a viable development platform for commercial applications, both locally hosted and remote.