The translation is a bit hard to read, but I can't believe any organization only has 70 trouble tickets in a month for 7,500 machines, regardless of the OS that is running.

The real problem here probably has to do with shared libraries. If you have a function in a shared library with external visibility, the compiler can't remove it, unless it is doing whole program optimizations across all of the programs, and I doubt the LibreOffice builds are doing that.

Given my experiences in Italy, if the neutrinos arrived exactly when they were supposed to, Italians would consider that about 15 minutes too early.

This is one reason there are so many JavaScript (perhaps actually DOM) questions -- where is the documentation to answer questions like "how do I do x, across every major browser versions which didn't really follow standards well"? If I'm programming in, say, Java or C++ with some framework where I control more of the environment, I can go to one place to answer questions, but there's no one definitive source for these cross browser problems.

The phrase "C/C++", that is.

C++, especially modern C++, is such a different language from C, that it makes no sense to talk about them as if they are the same. A decent programmer can learn everything they need to know about C in about two weeks. Modern C++ really takes years to really master. When I interview programmers, I'm immediately skeptical of anyone who claims to know "C/C++". Often, this means the most advanced "C++" feature they use is the // comment.

I always found PostgresQL harder to admin. It needs to be VACUUM'ed periodically. How often? The poor admin is supposed to figure that out themselves. Oh, and don't try to actually use the database during a VACUUM. Even after the autovacuum feature was added, it never seemed to work right, and my databases still needed to be vacuumed by hand, sometimes taking more than a day to run. Even with frequent vacuuming, indexes can get bloated -- I would see indexes with more pages allocated than entries, which needed to be manually reindexed. Worse, you need to tell postgres how much memory to allocate for vacuum'ing, and if you don't get it right, it 'leaks' disk space. None of these sorts of things have ever been a problem for MySQL.

There are many things which are not "being obvious to someone skilled in the field" but which are easy and cheap to duplicate once the original invention has been made and published.

That may be true, but consider that Lodsys hasn't made anything, and I guarantee you the Rovio developers hadn't read the patent before they wrote their games.

Sure about that? Confident that the Overdrive folks didn't hide some watermark of some kind into it? You better be sure, because the evidence is sitting on Amazon's servers...

I couldn't tell you if it is illegal or unethical, but emailing the DRM-stripped files to an amazon-hosted email server seems ... ill-advised.

JDK is so not GPL.