Mozilla's Mini-Me
An anonymous contributor writes "LinuxDevices has a story by the leaders of the 'Minimo' (Mini Mozilla) project, an effort to reduce Mozilla's code and runtime footprints and optimize its display for the small screens on embedded devices. The Minimo authors believe Minimo will become the browser of choice on embedded Linux devices with 64MB of RAM."
The Geronimo Project has been working on this same copncept for about 2 years now. Why reinvent the wheel?
Natural Selection: self-destruction of the poor and lazy
If you read the article, they are talking about rendering a fully compliant webpage. They did mention Opera and PocketIE. Both failed to render at 32MB. From the article:
"We have run the same tests using Opera and Pocket IE on 32MB device form factors, and neither can make it though the page load test based on their lack of browser content and standards support, or they just simply run out of memory trying to display the pages."
I don't think they are talking about the size of the binary distribution, but the size of all the components loaded into RAM and rendering compliant webpages.
"Rocky Rococo, at your cervix!"
Check out Konq-E. (Konquereor Embedded) It is stripped down Konq that runs against Qt and some stub KDE classes. Works really well! It renders web pages better than Moz, and for the performce/space/features it can't be beat, except for a few co mmercial offerings.. Oh yeah, did i mention full JAVASCRIPT? And it is based off of Konquerer 3.2!
Slashdot's rate-of-post filter: Preventing you from posting too many great ideas at once.
I love to break it to people when they just don't get it.
Firefox is only about an 8 MB download, and Mozilla is around 12-16. Sure, they're both bigger than Opera, but the size of the executable says nothing about how much memory it will use while running.
Okay, say you have a program that, when run, calculates the digits of pi. The program itself may be only a few tens of kilobytes, but it may allocate fifty megs or so as a holding area for calculations.
Or, an even more basic example:
while( true )
{
fork();
}
Compile it, and the executable is tiny. Run it, and it will quickly eat every bit of RAM in sight. With the loading of files, creating of data structures, caching of results, etc., it's unusual to find a program that doesn't use significantly more memory than is required to fit the executable alone.
Please, smoke less crack and get your act together.
You want the truthiness? You can't handle the truthiness!