Re: gtkhtml2 vs. gtkhtml1

Biswapesh Chattopadhyay <biswapesh_chatterjee tcscal co in> writes: 
> The problem with Gecko is the huge memory overhead it carries. I
> currently have the latest CVS mozilla built from sources with full
> optimization, release mode, stripped build, etc. TestGtkEmbed is using
> up 14 MB according to procman (showing http://localhost:10000/ - the
> webmin login screen). That's a lot of RAM just for showing a simple
> page.

I think it's a pretty acceptable amount, given what's involved. Modern
web pages are complicated, and there's a lot of infrastructure

> How about porting KHTML and KJS to GTK+2 ?

 - the main problem is not the initial port, but ongoing maintenance
   (1 full time person just to tread water), and catching up with
   evolving web standards (many more than 1 person)

 - khtml can't handle all the standards the gecko can

 - gecko is the AOL engine now so people will be testing web 
   sites with it, and AOL will be maintaining it and keeping it 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]