Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

On Wed, 2010-11-03 at 12:50 +0000, Ian wrote:
On Wed, 2010-11-03 at 07:09 -0400, Michael Meeks wrote:

At least then it would run on any platform with a JVM eg cell phone

    Sure any cell-phone with a vast amount of RAM, and a CPU twice as fast
as those we have currently in desktops might give reasonable

Ok, perhaps a daft suggestion but the principle is that all cell phones
will have a vast amount of RAM and fast CPUs in the next 2 to 3 years. A
gig of RAM is normal now, it would have been unthinkable 10 years ago.

Personally, a mindset such as "RAM is cheap these days, so let's waste
it" troubles me as a developer.  It's true that RAM is cheaper, but we
are not yet to the point where we no longer have to worry about runtime
RAM usage - far from it.

Just like consumers have managed to find ways to fill ever-so-increasing
hard disk space, developers will find ways to use up ever-so-increasing
memory space (and I've seen enough evidence of it).  So, we should
always be encouraging ourselves to reduce memory footprint, instead of
wasting it.

BTW, I love C++, which is standardized enough, is not tied to any single
vendor, and can generate native code, not byte code.

Just my opinion.


Kohei Yoshida, LibreOffice hacker, Calc

Unsubscribe instructions: Email to
Posting guidelines:
*** All posts to this list are publicly archived ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.