Whither javaworld.com?

I have been losing faith in javaworld.com lately. Maybe I've just advanced to the level of programming where I'm highly skeptical of programming advice dispensed by people who work in development environments that are highly dissimilar to mine. It's not that the advice is bad; it's just that it can't be applied in any practical sense to my environment, or it yields no benefit in my environment.

I still read javaworld.com from time to time, but this little nugget in an article describing cloud computing really makes me wonder:

"Likewise, you should not be concerned with writing application code to implement scalability, reliability, and other cloud and distributed computing features that a cloud platform could provide..."

Uh, right. I'll just store everything in Object[], read and write data using unbuffered classes, call read(byte b) a billion times instead of read(byte[]) once, etc., etc., because the cloud will manage scalability for me. WTF?

Building scalability into the application code is incredibly important. Likewise, if my application dies all the time, the proper solution is not just to let the cloud restart it and cross your fingers. The proper solution is to code the app so it doesn't crash. The article's advice is especially ludicrous because when you use the pay-as-you-compute model, application crashes waste your money because you're paying to crash and restart, instead of paying for your app to do something useful. Furthermore, if you build scalability into your app, your app becomes cheaper to run on the cloud because you use fewer resources (electrons, clock cycles, network, storage) to run it.