Agree. Java affect key components, not only extensions: base needs
java, and as consequence the bibliographic database too.
2010/11/2 T. J. Brumfield <enderandrew@gmail.com>:
I'm an user, and not a developer. So perhaps this is a silly question.
From a user's perspective, it always seemed like the Java portions of OOo
were shoehorned in. Starting a JVM eats up unneccessary memory and takes
time. One of the most common complaints of OOo is that it is a bloated app
that is slow and takes up too many resources.
I assumed that Sun kept the Java portions of OOo in since they liked to push
Java. In the age of netbooks, tablets and mobile computing, trimming the fat
becomes more important.
Would it be possible to remove the Java portions of LibreOffice and
reimplement them without the need to fire up a JVM?
Is there a technical advantage of running the wizards and such in Java that
I'm not aware of?
Thanks!
-- T. J. Brumfield
"I'm questioning my education
Rewind and what does it show?
Could be, the truth it becomes you
I'm a seed, wondering why it grows"
-- Pearl Jam, Education
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
Context
Re: [tdf-discuss] Java dependency · RGB ES
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.