linead

I wondered about this as well : https://www.researchgate.net/profile/Michael_Schappert/publi...

Seems like its a combination of cooling data centres (flowing air) and the quality of the air being circulated. So if there are pollutants in the air they pose a danger to the circuitry.

Never occurred to me this was yet another thing to be wary of when running a data centre!

The article is a little over-the-top on a few points. But this obviously stems from the authors own difficulties in choosing a name. While your mileage may vary if for examples you're choosing name in English, based upon a common phrase or word you're going to be hard pressed to get the first name that pops into your head.

I found it more disappointing that someone felt the need to "review" the blog post in the comment stream for us. Even if you disagree with the post it would be far nicer if you pointed in a nicer way and the fact that it 'landed on HN' should indicate that the communicated is interested in the content.

Can anyone explain why there would be hostility against this particular author? It seems a bit out of place in this community.

I never liked this argument. If you weigh up the disadvantage of the possibility of Steam going under in the future and your games being rendered unplayable with the advantages of instant updating, single social interface and ease of delivery that Steam provides I like to think that it's a good example of the consumer winning.

To me it's a bit like suggesting that you should just photocopy a book rather than buying it because if you buy it the pages may wear out one day.

from: http://www.sencha.com/forum/showthread.php?101713-About-Jack....

A few people in the community have been asking about Jack and his whereabouts as of late.

We're not entirely sure whether to respond to this with a 404 (not found), 301 (moved permanently) or a 307 (try again later at the same location.) After pretty intense work getting Ext JS established, Jack tapered down his involvement during the past 18 months. Although he may return in some capacity in the future, we wish him all the best.

But actually getting a document store on the client? A lightweight document store that supports complex object graphs?

I came across OrientDB a week ago, while looking for a Document DBMS that could be embedded in a client side application. Sadly haven't had time to fully check it out yet, but it looked the most promising of the options out there.

The Java/Hibernate pattern seems to be common for java applications, but there's doesn't seem to be (as far as I can see) for a document/object based alternative. I'm currently working with an object graph that translates very poorly to a relational DB, does anyone have any experience with any non-relational alternatives?