... you're an idiot, not "Enterprise IT".
You obviously don't work for my company.
Not when they cannot perform simple geometrical calculations.
http://www.wolframalpha.com/input/?i=triangle+with+sides+0.4592+meters%2C+0.6+meters%2C+0.6+meters
180 degrees, not 181, should be the sum of all internal angles.
Just turn in your geek card.
Please show us how you get any triangle with either more or less than 180 degrees as the sum of all internal angles.
Why don't they just grab the (say) 200 most visited sites on the internet, copy the JavaScript and use that to benchmark instead?
Simples.
That would likely be illegal.
I have to wonder why the cost is still so expensive.
The fabs used to manufacture these devices cost billions of dollars, not counting the R&D, labor, materials, etc.; consequently the amortized, sunk, and fixed costs quickly add to the product price.
If you have something more complex than a flat file, then use relational databases. Even Access databases are better than a collection of text files.
That really depends on what your intended use for them is. I mean I don't know this particular fellow's situation for data collection or what tools he uses for reporting and visualization but perhaps, for him, it's a much better idea to store them in flat files. Me? I have been using flat files for all my data collection about local crime (see here, here, here, and here) for several reasons:
1. I script it all with awk/sed to scrape the data and then put it in a CSV for summary with PostgreSQL.
2. Yes, I could use PostgreSQL for it all but I like to easily see it in its raw format on another remote machine. I also like to use Excel to do ad-hoc pivots and this is the easiest way for me to do that.
3. I upload the data to Google Docs and use their gadgets to make charts for my dashboards and maps. If I were to store it solely in PostgreSQL I would have to make the CSV, pipe it into the PostgreSQL, convert it back out to CSV and then upload it. An additional step for nothing.
Hey, no method is perfect for everyone and every project is a little different and while it's hard for me, based on the information provided, to give this guy any help, automatically suggesting that he needs a relational database to do his data storage might be just a little shortsighted.
YMMV.
There, fixed that for 'ya.
"It is better for civilization to be going down the drain than to be coming up it." -- Henry Allen