Myk Melez wrote:
David Ford wrote:
Even with tuning, FF is a dastard piggy. I've tested things with FF.
Start it with no history, no recovered session. Load up digg.com and do
nothing. Just let it sit there. It will sit there and slowly grow and
grow and grow. The caching isn't the
David Ford wrote:
Even with tuning, FF is a dastard piggy. I've tested things with FF.
Start it with no history, no recovered session. Load up digg.com and do
nothing. Just let it sit there. It will sit there and slowly grow and
grow and grow. The caching isn't the problem, that's tunable.
On 5/11/07, Ian Stirling [EMAIL PROTECTED] wrote:
The big problem is the lack of debug tools.
I write a new extension.
I then want to profile it, to find out how much CPU, and how much CPU it
makes the core use.
I can't.
Worse, the same problem applies to most of the XUL/XBL/JS core.
I was
Hi
Or opera of course... it went fully open-source didn't it?
No it's not. It's just free.
I'm wondering why nobody seems to consider webkit as the viable alternative:
* it's open source
* it's been ported to qt recently, which may lead openmoko to use qt libs
* there is a registered google
Florent THIERY writes:
I'm wondering why nobody seems to consider webkit as the viable
alternative:
I'm sort of missing why you seem to feel webkit isn't a viable
alternative -- I've never worked with it at all, but you seem to be
giving a bunch of reasons why it's likely to be just that by the
On Fri, 2007-05-11 at 16:12 +0200, Thomas Gstädtner wrote:
As announced this is a long term project, so there will be no firefox
mobile in 2007 and maybe not in 2008.
Firefox doesnt only use a massive amount of RAM, it also needs a
powerful CPU.
Imho a browser based on KHTML/WebKit,
[EMAIL PROTECTED] wrote:
yowza!
Looks like our favorite Web browser is about to go mobile.
Mozilla head honcho, Mitchell Baker, told the folks at APC magazine
that Mozilla is working on a Firefox to go for your cellphone. It's a
long-term project (meaning it's not coming out any time
David Ford wrote:
I used to love FF, now it's just a cpu/ram hog that usually gets killed
by the kernel every 36-48 hours for taking about 2G of ram.
Memory leaks in Firefox (as opposed to high memory consumption
generally, which as Bradley notes is often caused by Firefox's agressive
David Ford wrote:
If it's anything like mozilla/firefox now, we're gonna need a hefty
battery, hugely more cpu, and about 1G of ram onboard.
Oddly.
It seems to behave OK on my laptop - 1.5 - which I was using for some
time with 128M RAM.
Admittedly, it did need restarted every day or three.
As announced this is a long term project, so there will be no firefox mobile
in 2007 and maybe not in 2008.
Firefox doesnt only use a massive amount of RAM, it also needs a powerful
CPU.
Imho a browser based on KHTML/WebKit, especially S60WebKit would be the best
choise.
Whoever has used one of
here is a test of minimo 0.2:
http://ekstreme.com/thingsofsorts/fun-web/first-look-at-minimo
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
While FF does have a fairly large footprint, I've never had these kinds
of memory consumption problems. I generally leave my FF sessions open
for days or weeks at home, and I simultaneously load 3D games, OOo,
graphics apps, and other stuff without ever having trouble with memory
(granted I do
Bradley Hook wrote:
That said, the full blown browser would be an awfully hefty app to put
on a phone, and the minimo browser is currently targeting windows
portables. Why not go with something with a tiny footprint, time-tested
and proven lynx anyone?
i would prefer w3m or some other
For the same reason I use open office instead of vi. Lynx is far from
capable.
Even with tuning, FF is a dastard piggy. I've tested things with FF.
Start it with no history, no recovered session. Load up digg.com and do
nothing. Just let it sit there. It will sit there and slowly grow and
yowza!
Looks like our favorite Web browser is about to go mobile. Mozilla head
honcho, Mitchell Baker, told the folks at APC magazine that Mozilla is
working on a Firefox to go for your cellphone. It's a long-term project
(meaning it's not coming out any time
If it's anything like mozilla/firefox now, we're gonna need a hefty
battery, hugely more cpu, and about 1G of ram onboard.
I used to love FF, now it's just a cpu/ram hog that usually gets killed
by the kernel every 36-48 hours for taking about 2G of ram.
The mozilla team needs to figure out how
16 matches
Mail list logo
