nslater

I call BS. There is a snowball's chance in hell Facebook have seen this, let alone approved it. One of the options is to defriend everybody. How is this not a malicious action?

Facebook can't revoke the API, because the site clearly states in the footer that "Buddy Hack in no way encourages the usage of any Facebook account other than your own." That seems waterproof to me.

Rendered once and cached? The cached GIF is rendered each time as well. As far as I know, it's not possible to cache a rendering. There are still calculations to do each time you want to convert the cached data into an image. The question then becomes, which calculations take longer. The calculations needed to convert the CSS into a bitmap for the screen, or the calculations needed to convert the GIF data into a bitmap for the screen. I'm betting the difference is negligible.

(If I have misunderstood some step of the rendering process, I would love to know how, or what. I don't know much about graphics processing, so I am unaware of any caches beyond what the browser maintains.)

I wouldn't say this is part of an intentional standardisation effort, but we worked closely with the Cordova team on this.

If other projects want to co-ordinate with us, I would welcome that.

Just to clarify, the Couchbase product is a backwards-incompatible fork of Apache CouchDB.

Apache CouchDB remains the original CouchDB.

It is where most of the developers are, and where most of the community is.

The one and only! HUZZAH! ;)

Sure, JSON seems to have lots of uses.

I know a few people who've been working on a JSON Schema for the more formal datasets. I worked on an Internet Draft for this for a while, before the effort crumbled. Like most of the Web though, JSON really tends to shine when it is semi-structured — with any additional structure applied to it, post-hoc, by the consumer. CouchDB is a good example of a system that embraces this property.

I wasn't actively involved, but as far as I know, the old Atom wiki was the birthing place of Atom. Sam Ruby hosted it on his site, and got a lot of discussion around the idea of a new syndication format. I believe it was called Echo for a long while.

http://intertwingly.net/wiki/pie/FrontPage

Do you mind if we quote you on this?

When do we get a hosted in-document commenting system?

What, with his comment about being able to eventually understand sociology using physics, I think this essay is easily 3 Cuil.

So much fail.

Easter Eggs, illegal in most countries. Now you know.

It's still very early days. If you want do do a very large production setup of CouchDB, you will be sitting on the bleeding edge of community experience. That's not for everyone, of course.

Nope, it's really not meant to be. But it is intended as a primer for those coming from a relational database background. CouchDB is NOT a replacement or an alternative to relational databases. CouchDB is fundamentally a different way to model data. That may work for you, it may not. CouchDB is not a panacea.

If you need to wait for wide adoption in the hosted server market place, this seems like a sensible concern. You can install CouchDB by hand of course, it's really not that hard.

The API changes occasionally, as is natural. The project is improving as we get more popular and people suggest new and better ways of doing things. This is part of having a healthy free software community. It's important to point out that the API is so simple it's crazy, and it changes very infrequently - so it's really not much of an issue.

Wait, what? Where does it say we're an alternative to relational databases, or MySQL?

Hey David,

We would be interested in having your feedback on the official mailing list where we could discuss your concerns. The problem with the first two chapters is that we're trying to address the needs of a wide range of readers. We wanted to cover the major differences between CouchDB and an RDMS from “10,000” feet.

Again, thanks for the feedback - we would love to have you on the mailing list.

Noah