Skip to main content

How to do an already doomed test

Read this blog MS Office 2007 versus Open Office 2.2 shootout. The test was already flawed from the beginning for the following reasons:


  • The author did not upload the original file which is probably a Excel 97 xsl file as a reference


  • Instead, two different formats were used: one from OpenOffice 2.0 beta sxw which is a compressed file and other a xml file from Microsoft Office 2003.


  • Since two different formats were used, the test is automatically void of meaning because of the lack of the original file.


  • Renaming the xml file to xsl like the author, I verified if it can be read with OpenOffice 2.2. It does not because the data is interpreted as xml which will exceed the limit of row in Calc application. Office Excel 2003 will render like a spreadsheet due to proprietary XML parser. However, Excel 2003 cannot read sxc nor OpendDocument Spreadsheet unless SUN's Open Document Format plugin is used.


  • The test is unrealistic in real world business because of the size (273 Mib of spreadsheet data). According to the author, the spreadsheet is actually a log file. One has to wonder why using a spreadsheet application to archive log.

Comments

Stephen Smoogen said…
As horrible as it sounds.. I have regularly seen 100+ MB excel spreadsheets with log data and other stuff in it.

Remember to look at the problem from a Windows users perspective. You have large amounts of data you want tabulated, and you have a very limited amount of tools to do it with. You can import the file into word, but it wont be able to correlate all the events together. So you import it into excel and have a column for time, for type of events, and data. Tada, now you can use a tool you are familiar with to manipulate the log data. (and you can use things like normalization etc if you need statistics). Is it optimal.. no.. but it is a matter of what tools you know. [I mean how many perl/awk/python programs do exactly the same thing because each specific author knew what one tool to write it with.]

Popular posts from this blog

Drawing hair with Inkscape

My very first online tutorial is an adaption from Chris Design Drawing Hairs article using both Path and Path Editor tools which requires Inkscape 0.47 or newer. Start-up Inkscape application which should open a new blank page and set the document into landscape.  Create a path Select the bezier tool or press either Shift+F6 or B on the keyboard. Draw a line to approximately 800px or more. You can also use rectangle tool ( R or F4 as shortcut key) as a thin line illustrated in grey. While the line is selected, convert into path from the menu Path -> Stroke to Path or press Ctrl+Alt+C on the keyboard. For the rectangle, Path -> Object to Path or Ctrl+Shift+C . The result will show grey diamonds on each corner. Create a pattern On the menu, Extensions -> Modify Paths -> Add Nodes . Set the Max Segments Length to 5px. On the menu Extension -> Modify Paths -> Jitter Nodes . Leave the default settings and apply effects.

HP, Linux and ACPI

 Majority of HP hardware running on Linux and even Microsoft reported an issue related to a non-standard compliant ACPI. Notable message below repeats at least three times on the boot: 4.876549] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190215/dsopcode-198)  [ 4.876555] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190215/psparse-529)  [ 4.876562] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190215/psparse-529) The bug is a known for years from which Linux kernel team are unable to fix without the help of vendor i.e. HP. Here is a compilation of reports: BIOS error: The BIOS in this system is not fully ACPI compliant. ACPI BIOS ERROR (blue screen) on startup   ACPI bad works with Linux    The good news is some errors seems harmless. Unfortunately, such errors displayed the quirks approach used by

Detailing the installation of AMD OpenCL rpm for Fedora

Revisiting the previous blog and freshly reinstalling Fedora Design Suite due to a busted boot, I look at the official guideline from AMD Driver for Red Hat Enterprise Linux 7.2 and write a way to improve the process of installing on Fedora 29 in this example. Extracting the tarball contains the following: amdgpu-install amdgpu-pro-install symlink to amdgpu doc folder repodata folder RPMS folder containing rpm package Executing the command ./amdgpu-install -opencl=pal --headless sadly failed on Fedora on that line: ./amdgpu-install -y --opencl=pal --headless Last metadata expiration check: 0:30:51 ago on Mon 19 Nov 2018 07:13:43 PM PST. No match for argument: amdgpu Upon closer look, the script failed to created a temporary repository on /var/opt/amdgpu-pro-local probably explaining why amdgpu metapackage name failed to display. Someone should investigate and provide a fix. At least, we find out Fedora support is available but unofficial. Due to its design, Gnome