2007/4/29, Kirill S. Palagin <[EMAIL PROTECTED]>:

> -----Original Message-----
> From: Michael Adams [mailto:[EMAIL PROTECTED]
> Sent: Sunday, April 29, 2007 7:22 AM
> To: [email protected]
>
> Microsoft Office
><snip>

I do not give a damn about their office, because I do not generally use
it.

> OpenOffice.org
> ==============
> 1. Loads the core component to run all applications when the
> first is loaded. Better integration between components is the
> desired objective.

You mean that even if user does not need any other part of Office,
he/she would still pay the tax?
Of maybe you mean crash/hung in one app would bring down all the
documents at once is "better"?

> 2. Is multi-platform (Windows, Mac, Linux, and Solaris) which
> includes loading the java core for some aspects to run. Java
> itself is multi platform.

This is of importance to IT departments (even is user is it's own IT
dept), not end users.

>
> A comparison of resources used when copying and pasting from
> Excel to Word, versus Calc to Writer on Windows, Mac, and
> Linux would also be useful. I'm not saying OO.o would be
> faster than MSOffice but I feel it would be a much closer

I have tested by copying table of 7000 rows by 26 columns from
spreadsheet to database.

MSOffice 2003 (sorry, I do not closely follow trends and do not have
Office 2007)
Excel to Access - 45seconds

OpenOffice 2.2
Calc to Base - 1m40 sec (6 minutes, if you enable primary key creation).


Since they say that MS Office is 10-100 times faster than OpenOffice.org, I
am surprised that the difference was not much bigger (greater? Sorry for bad
English)!


http://www.openoffice.org/issues/show_bug.cgi?id=76606

> contest. Oh, does MSOffice 2007 work on WINE on Linux yet?

Since you insist - Office97 in WINE starts 3 times faster than
OpenOffice2.1 (Linux) on the same machine. Office97 is functionally
sufficient, so I do not care about 2007.

People, we have to admit that we have performance problems and the
problems are not being addressed because of lack of resources.

Regards,
K. Palagin.

Reply via email to