But after those measures the climate still will be changing (as happened from the start of the times).... what we need is a new technology (and science) for total climate control in order to suppress any change for ever.

I'm sure Microsoft can point to millions of users in lots of statistics and hundreds of focus groups about people liking clippy.

And is the same with the 99.9% of the experiments the scientists do: people just don't believe (how many experiments about potentially successful treatments for AIDS/Cancer/whatever get published on the news... who cares?)

For people to believe at heart in this or that thing, they need to see something working based in that experiment.... for example, "a new big touristic project for a new beach created (as predicted) by the GW".

Tsunamis, earthquakes, etc don't count... they are too random and always can be attributed to non natural sources.

In your view, a similar agreement with Google would also be prosecuted...

The O/R impedance mismatch may be a mental block but not the O/SQL one.

This complicates as the DBMS vendors are really good at improving SQL queries that doesn't necessarily fit the object model or the mapping layer.

For non trivial projects you end up applying the O/R mapping to replace the trivial SQL sencences, and the "raw" SQL (or even stored procedures) for the contrived or performance critical cases... which in the long term is a PITA.

> There's not even one Game, each is playing his own and wanting to "win" by whatever internal definition they have.

You need money to play any game, by whatever internal definition you have. And more to win... or because you win.

BTW, even if the CEO's priority is not the money, the shareholders (and most of the workforce) usually think different.

Apparently just the chapter 7 is about the XX:

  Chapter 1: Strategies, Approaches, and Methodologies, Chapter 2: Operating System Performance Monitoring, Chapter 3: JVM Overview, Chapter 4: JVM Performance Monitoring, Chapter 5: Java Application Profiling, Chapter 6: Java Application Profiling Tips and Tricks, Chapter 7: Tuning the JVM, Step by Step, Chapter 8: Benchmarking Java Applications, Chapter 9: Benchmarking Multitiered Applications, Chapter 10: Web Application Performance, Chapter 11: Web Services Performance, and Chapter 12: Java Persistence and Enterprise Java Beans Performance.

BTW, of course you should avoid the XX options, but when in need, it is better to have some authoritative reference than having to rely on the uninformative Oracle docs or random forums.

I'd like to add Hermann Hesse's Sidartha and (if you have more time) The Glass Bead Game. Great and entertaining readings.

And for another kind of classic, despite the Rampa's fiasco, The Third Eye is also a very nice story.

Same here. Recently I had some issues with fonts that were solved by switching to sun-java from openjdk (along other measures.) Sadly that issue was mandatory for my app.

For the time being, I'll have to disable all updates on those PRODUCTION machines in order to avoid the application from being stopped.

I don't understand why Cannonical can't just show a message declaring sun-jdk as deprecated.

Many times with a (semi)broken operating system, you don't have all the usual tools.... sometimes your only clue is a syslog driven console text message.

Right... at that time I (in Peru) had no idea of the BSDI issue, yet Red Hat, Slackware, SoftLanding and others provided decent (for the time) fdisk-based installers and most of the cheap hardware was fairly supported. Soon came the LAMP stack...

> It's the same comment over and over again, who mods this up?

The same people that submits this story over and over again.

I hope that the KDE folks don't get infected with the tablet flu for at least 10 years on. I'll try kubuntu 11.10 in a VM getting ready for a full reinstall of my machines with the 12.04.

Yep... imagine having to pay several $K for background antivirus software running 24x7.