1. If you're going to write a "demo app", why not write one that is in the niche that you are targeting. I understand messaging is not it.
2. "The second set of detractors say realtime applications shouldn't go to disk, because it's slow and a lot of data. To them I say "disk is free"" I think in many applications it's safe to say that disk space is free, but disk access time certainly isn't, especially if you're syncing transactions to disk on commit.
3. "Call me when performance matters." You can write nifty apps with little code in many languages/frameworks. The question is, what happens if the shit hits the fan?
4. Hacker News load probably isn't that high. It's certainly not the same as the "slashdot effect".
5. "the important thing about this demo is the web ... your applications can be deployed anywhere there's a CouchDB." - I really don't understand this point. The same applies to AMP or Tomcat+Mysql+Java. If it's there you can deploy it. What's P2P about it? I can write Java code that speaks to other Java code on another Tomcat server, and it's not even particularly hard, as there are frameworks for it. I don't like Java, but then again, I don't like JavaScript either.
6. "Actually, there isn't much complexity to hide as CouchDB is simple on the inside as well." As a user, I don't care. The point of systems programming is for engineers to sit down and write hi-performance C/C++ code that will then be used by thousands of developers to run billions of transactions for several years. If the engineers spend an extra month to make it 10% faster, then it's worth it, because it will be used by so-many people for a long time.
2. "The second set of detractors say realtime applications shouldn't go to disk, because it's slow and a lot of data. To them I say "disk is free"" I think in many applications it's safe to say that disk space is free, but disk access time certainly isn't, especially if you're syncing transactions to disk on commit.
3. "Call me when performance matters." You can write nifty apps with little code in many languages/frameworks. The question is, what happens if the shit hits the fan?
4. Hacker News load probably isn't that high. It's certainly not the same as the "slashdot effect".
5. "the important thing about this demo is the web ... your applications can be deployed anywhere there's a CouchDB." - I really don't understand this point. The same applies to AMP or Tomcat+Mysql+Java. If it's there you can deploy it. What's P2P about it? I can write Java code that speaks to other Java code on another Tomcat server, and it's not even particularly hard, as there are frameworks for it. I don't like Java, but then again, I don't like JavaScript either.
6. "Actually, there isn't much complexity to hide as CouchDB is simple on the inside as well." As a user, I don't care. The point of systems programming is for engineers to sit down and write hi-performance C/C++ code that will then be used by thousands of developers to run billions of transactions for several years. If the engineers spend an extra month to make it 10% faster, then it's worth it, because it will be used by so-many people for a long time.