Daniel Glazman wrote on 19.01.2006 14:11:
Peter Reaper wrote:
I have my VOIP client (currently Google talk) running im my system
tray taking up only 3.5 MB RAM. To have VOIP available as a Firefox
extension all the time would require me to have Firefox running all
the time, which takes up about 30+ MB RAM (on startup!) *plus* the
Wengo Extension.
No. And you can trust me on that...
That's precisely 26 megs *with* the Wengo extension, but one dll is
built debug and not opt, and I have at least a dozen extensions in my
profile
and a quite large personal bookmarks toolbar, so you can expect a lower
footprint.
Well, *my* task manager showed 30 MB RAM *without* WengoPhone (I have
three startup pages. I closed 2 of them, then "measured"). YMMV.
The main point still remains valid: Most users will *not* want to have
to load their browser to make a phone call, or keep their browser loaded
to receive calls. And the RAM used is still ~7x that of Google Talk (25
MB vs. 3.5 MB).
I'm sure it's a "cool" Extension, but I wouldn't rely on it being the
*primary* vehicle for WengoPhone usage. (just my € 0.02)
PS. Julien's statement that the Extension could be a kind of stepping
stone to a full XULRunner application makes a lot of sense to me.
--
Regards,
Peter Reaper
The browser you can trust: http://www.GetFirefox.com
Reclaim Your Inbox: http://www.GetThunderbird.com
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
