PDF size is definitely bloated, ODF is not
on
OpenOffice Bloated?
·
· Score: 1
As a quick-n-dirty test I used a PC running Windows 2000, OpenOffice.org v2.0 and MS Office 97 to build.pdf files of quotes submitted to me as an Excel spreadsheet (one printed page) and a Word document (8 pages). The.pdf engine used with word and Excel was Software995's pdf printer driver. I accepted the default settings for pdf creation in both OOo and MS Office apps.
The OOo spreadsheet.ods was 16K, the Excel spreadsheet.xls was 24K in size. The OOo document.odt was 38K, the Word document.doc was 131K in size. In fairness, the documents did contain VB macros that the.odt file did not save. The OOo spreadsheet.pdf was 120 KB , the Excel spreadsheet.pdf was 32KB in size. The OOo document.pdf was 200KB, and the Word document.pdf was 100KB in size. I will check PDF creation on these same documents from my Linux box at home to complete the comparison. My curiosity will then be satisfied.
To me, the expense of archiving data files is of greater interest that the expense of RAM needed to support the software. I must archive documents for many years. Disk space requirements are constantly growing, while the RAM in each PC is reusable.
It's an agreement thing. You agree to an abridgement of your constitutional rights to receive the "benefits" offered by whatever induces you to become a party to the contract. In this case, the kids parents agreed to have the restrictions placed on their minor children.
The key is motivation, and your valuation of those motives. Ask yourself "Why ?"
Why did id change Q3A? Product improvement, or mod breakage?
Why did MS change default message formats? Message improvement, or to promote a single-source product?
Answer those questions for yourself (honestly) and draw your own conclusions.
Yes, changes you make to a GPLed program are yours. To have and to hold, in sickness and health, yada-yada-yada. The point of the matter, as I see it is 'What can you do with your changes?' You can keep them secret. Go ahead. Make your changes, but keep them to yourself. The GPL does not require publishing your source code, until you distribute binaries. If you want to build on GPL code for your own use, fine. Go ahead, RMS doesn't mind. Ask him. You can share them. If you want to contribute your work (or even just some of it) to the community, fine. That's how the code you used got there in the first place. What can you not do with your changes? Distribute binaries without the source code. If you want to receive money for hidden-source software, earn it. Write your own code - all of it. If you are concerned about protecting your IP, you may be confusing the GPL and BSD licenses with the Microsoft EULA. Or did I not understand your position? Just my day's wages.
If I remember correctly from my projectionist days, 35mm film has 24 frames/second. The frames are physically about 1" in length, and a single shipping reel holds up to 20 minutes of film. So we get 2 ft * 60 sec * 20 min = 2400 ft * $61/ft for a total of $146,400 for Deluxe's lab to process 20 minutes of film.
The remark about CPU cycles used for fluff like dancing paperclips was hyperbolic. A little extension along one axis (amount of fluff) yields a great extension along another axis (increased CPU utilization). Of course, I exagerated a little.:-)
But just a little. Win 9x inefficencies and Office-bloat sold as many, if not more, Pentium/PentiumII class chips as applications that really needed the power.
Yes, I've used Office. It contains nice applications covered with a thick layer of gooey (GUI?) chocolate to raise the sweetness level (cost of the product, cost of the recommended hardware) and put smiles on the faces of the users.
By the way, have you ever used the fish scaling utility hidden in the Windows 2000 Beta 3 Programs/Accessories/Entertainment/Sports/Weekend/ FoodGathering/Beer Drinking menu?;-)
Right! M$ Ofice has "Clippy", the animated assistant (more wasted CPU cycles == justification to upgrade to that PentiumIII/500). Now KOffice has to have one.
M$ Office has security holes everywhere you look. Is this also a "feature" KOffice must have before you try it? I would prefer not to let someone else flatten my hard drive.
I suggest re-thinking this "feature" bloat mindset. It diverts CPU cycles into useless, cutsey, Bill-Gatesey garbage (like Bob) and developers' attention from useful avenues of thought and activity.
Slashdot Mirror
The OOo spreadsheet.ods was 16K, the Excel spreadsheet.xls was 24K in size. The OOo document.odt was 38K, the Word document.doc was 131K in size. In fairness, the documents did contain VB macros that the .odt file did not save. The OOo spreadsheet.pdf was 120 KB , the Excel spreadsheet.pdf was 32KB in size. The OOo document.pdf was 200KB, and the Word document.pdf was 100KB in size. I will check PDF creation on these same documents from my Linux box at home to complete the comparison. My curiosity will then be satisfied.
To me, the expense of archiving data files is of greater interest that the expense of RAM needed to support the software. I must archive documents for many years. Disk space requirements are constantly growing, while the RAM in each PC is reusable.
It read that way because the full text of the story was lifted from the story on The Register.
Moving to a Linux desktop isn't a deliverance to a computing valhalla.
Unless you run Red Hat...
It's an agreement thing. You agree to an abridgement of your constitutional rights to receive the "benefits" offered by whatever induces you to become a party to the contract. In this case, the kids parents agreed to have the restrictions placed on their minor children.
The key is motivation, and your valuation of those motives. Ask yourself "Why ?" Why did id change Q3A? Product improvement, or mod breakage? Why did MS change default message formats? Message improvement, or to promote a single-source product? Answer those questions for yourself (honestly) and draw your own conclusions.
Yes, changes you make to a GPLed program are yours. To have and to hold, in sickness and health, yada-yada-yada. The point of the matter, as I see it is 'What can you do with your changes?' You can keep them secret. Go ahead. Make your changes, but keep them to yourself. The GPL does not require publishing your source code, until you distribute binaries. If you want to build on GPL code for your own use, fine. Go ahead, RMS doesn't mind. Ask him. You can share them. If you want to contribute your work (or even just some of it) to the community, fine. That's how the code you used got there in the first place. What can you not do with your changes? Distribute binaries without the source code. If you want to receive money for hidden-source software, earn it. Write your own code - all of it. If you are concerned about protecting your IP, you may be confusing the GPL and BSD licenses with the Microsoft EULA. Or did I not understand your position? Just my day's wages.
If I remember correctly from my projectionist days, 35mm film has 24 frames/second. The frames are physically about 1" in length, and a single shipping reel holds up to 20 minutes of film. So we get 2 ft * 60 sec * 20 min = 2400 ft * $61/ft for a total of $146,400 for Deluxe's lab to process 20 minutes of film.
The remark about CPU cycles used for fluff like dancing paperclips was hyperbolic. A little extension along one axis (amount of fluff) yields a great extension along another axis (increased CPU utilization). Of course, I exagerated a little. :-)
/ FoodGathering/Beer Drinking menu? ;-)
But just a little. Win 9x inefficencies and Office-bloat sold as many, if not more, Pentium/PentiumII class chips as applications that really needed the power.
Yes, I've used Office. It contains nice applications covered with a thick layer of gooey (GUI?) chocolate to raise the sweetness level (cost of the product, cost of the recommended hardware) and put smiles on the faces of the users.
By the way, have you ever used the fish scaling utility hidden in the Windows 2000 Beta 3 Programs/Accessories/Entertainment/Sports/Weekend
Right! M$ Ofice has "Clippy", the animated assistant (more wasted CPU cycles == justification to upgrade to that PentiumIII/500). Now KOffice has to have one.
M$ Office has security holes everywhere you look. Is this also a "feature" KOffice must have before you try it? I would prefer not to let someone else flatten my hard drive.
I suggest re-thinking this "feature" bloat mindset. It diverts CPU cycles into useless, cutsey, Bill-Gatesey garbage (like Bob) and developers' attention from useful avenues of thought and activity.