Post a Comment
No, something entirely different. Minimo is dead. This is an attempt to provide something much more akin to the desktop version of Firefox.
'Specifically, Mozilla will add mobile devices to the first class/tier-1 platform set for Mozilla2, the next-generation browser technology due in 2008, Schroepfer wrote. "This means we will make core platform decisions with mobile devices as first-class citizens. We will ship a version of "Mobile Firefox" which can, among other things, run Firefox extensions on mobile devices and allow others to build rich applications via XUL.'
Note that Mozilla2 is effectively the same thing as Gecko 2, and not to be confused with Firefox 2, which is already out of course...
Well, I'm using firefox x64 (64bit programs tend to use more ram c.f. boundary alignment) and google takes up 30Mb Ram (31 actually).
So you're off by a factor of 2. Of course if you've installed the special I'mAnMSShill extension that reserves 32Mb ram for the fun of it, then I could see where you've got the extra 30Mb from.
Edit: Compare that to IE64 that gets to 39Mb, and I'm really not sure which is more of a memory hog.
Edited 2007-10-12 11:13 UTC
...of software and hardware development is becoming more and more centered on the embedded space. No wonder Firefox want a peace of the pie.
I wonder if they can cut down the behemoth that is Firefox enough to compete with the like of Opera? Somehow, I get the feeling that, having witnessed the stellar rise of Firefox from the beginning, it won't take to long.
I wish some of the Linux distros would take the same approach. Microsoft has by no means dominated the mobile device world, the way they've dominated the desktop. Of course, getting a new OS onto a mobile device is a lot harder than getting a new application installed.
Who said anything about them not having a stake in it? I just said they haven't got it locked down the way the have with desktop market. There's lots of room for competition in the pocket. Given the way Opera have been so successful in the mobile browser market, surely Red Hat or SUSE would fancy a shot at beating MS in this rapidly growing arena?
(posted on Windows Mobile 2003SE, Opera Mobile 8.6)
"I wonder if they can cut down the behemoth that is Firefox enough to compete with the like of Opera? Somehow, I get the feeling that, having witnessed the stellar rise of Firefox from the beginning, it won't take to long."
I find it more likely that they'll implement memory swapping by hand. Symbian OS 9.3 onward already implement demand paging...
Now, quite frankly, would the mobile vendors please take their heads out of their rears and include decent amount of RAM on their devices? What's up with Nokia bundling odd numbers like 45MB on the E70 for example? And leaving at best 22MB of free RAM for applications. And the horrid memory leak that lowers this to 14MB after light usage of the S60 browser and a couple J2ME midlets?
I'd rather have abundant RAM and just enough builtin Flash to store the firmware and perhaps 8MB of user data, and have everything else go to a memory card. That's a tradeoff I'd gladly make. Make it mandatory to use 150X SD cards, I don't care! But the out-of-memory situation on most mobile devices is so damn annoying that I don't even know where to begin.
The Wii has 31% less RAM (and I'm being really nice to Nokia by including the Wii's video RAM on this calculation) than the revised 8GB Nokia N95, and yet it's capable of so much more. The Internet Channel Opera doesn't bomb out of memory nearly as frequently as Symbian versions. And ARM machine code is so much denser than PPC's. This points squarely to Symbian's inefficiency at handling memory.
This said, I believe Firefox has nowhere to go but Pocket PCs. Symbian is a dead end. It can't handle this kind of stuff.
Unless they go Opera Mini's route and offload most of the DOM processing to an intermediate server, and only deals with presenting constructed, laid out pages. They won't need anything more than a Cairo canvas and a stream of drawing instructions, and some interpreter to handle transformed Javascript code. But that rings as a 3rd party opportunity, no?
Any intrepid souls willing to try? Maybe we can build a startup =P
:)
What a horrible story.
Basically, they are saying: small devices and the embedded space is too low powered to run web browsers and they are getting more powerful so we can move there... and somehow this is revolutionary.
""Getting a no-compromise web experience on devices requires significant memory (>=64MB) as well as significant CPU horsepower," Schroepfer added"
Excuse me? What is this "no-compromise"; does he believe that only Firefox is the "no-compromise" solution?
Yet again it seems that the Mozilla mob are re-writing history to suit themselves.
If you want to visit say: the Steam website, you you have lots of layout, many MB of Images, streaming video, Flash, Javascript, all jumbled together.
Displaying that correctly is a 'no-compromise' web experience. And I would be surprised if it could be done in less than 64Mb of Ram with any browser at any reasonable speed. As Rasterman says: It's amazing what a little cache can do to your life.









