Summary:

There are two sides to every story: cloud computing might be a problem or a solution; the responsibility for online privacy might lie with web sites or the government; the ideal server might be either underpowered or overclocked; and Oracle might or might not ruin Java.

heads or tails

Today’s links reinforce the notion that there are two sides to every story: Depending on whom you ask, cloud computing might be a problem or a solution, online privacy might be best addressed by regulating either web sites or the authorities, the ideal server might be either underpowered or overclocked, and Oracle might or might not be ruining the Java community.

Consider The Cloud As A Solution, Not A Problem (From the Forrester blog) This isn’t a new idea, but I’ll point out every blog and article reinforcing it until it becomes the norm. Cloud computing isn’t about doing the same old stuff via the web; it’s about doing something new because of the web.

US Calls for Online Privacy “Bill of Rights” (From Ars Technica) Here’s an idea for the U.S. [government]: Get your own privacy act in order first before taking web sites to task. We’re how many years in, and it took a court to finally protect email under the Fourth Amendment?

SGI Forges Overclocked Servers for Wall Street (From The Register) We talk a lot about servers running low-power chips to avoid overprovisioning and the resultant power bills. Here’s the opposite — and equally awesome — end of that spectrum.

Oracle vs. Who’s Next? (From People Over Process) This is a good assessment of the general malaise surrounding Oracle’s treatment of Java. Not that anything should be surprising when it comes to Oracle and making money.

Today’s Cloud Computing Landscape [Infographic] (From Wikibon) I like the idea, but there are some notable omissions — Red Hat, CA and Salesforce.com to name a few.

For more cloud-related news analysis and research, visit GigaOM Pro.

Image courtesy of Flickr user Lin Pernille Photography.

You’re subscribed! If you like, you can update your settings

Comments have been disabled for this post