Time to Relox.
Erlang sucks, big time. So does Java. Join us now and continue development of a software that isn't shackled to the BEAM, HYPE, J2E or any of these other so called technologies.
CouchNG is going to be a refactoring of CouchDB interly in the Java-Script and XHTML programming environments using real development methodologies on go-forward basis to maximise the synergistic nature of the open saurce comminity.
Put simply, CouchNG will be a highly interactive, distributed, document-oriented predicate-based experimental BETA weblication built using the worlds most advanced HTML. With hundreds of so called applications promising to change your life, there was nothing that gave an exact functional, implementational or sociological match across the multi-faceted Web 2.0 environment we live in… until you drink your problems away and relax on the Couch, the CouchNG.
Imagine a standard, a standard done properly. Imagine seeing the little badge on a website, news feed, wap portal or mobile computing device and knowing that it would work. CouchNG gives you that comfort. We’re already seeing Couch compatible websites. We’re in a time limited exclusive BETA period so we need you to start Couching right away. Use it, mash it, live it and breathe it in a world that works.
The primary API for programmatically accessing the CouchNG database is a REST API. That's right, REST on the Couch. Doesn't that feel nice? Let me fetch you a double whisky and a cigar.
“This is AMAZING! Got it to work in about 3 secs! This is Couchingly easy!”
“CouchNG is the next best thing to canned SPAM.”
“Very impressed with CouchNG so far. It has enabled me to start building numerous collections of Deferred Actions, a process I've named Couching, and for those procedures that cannot be dealt with by Couching, I've managed to break them down into Cushions.”
“I added three inches with CouchNG in just 30 days.”
“Few people realise the magnitude of the impact CouchDB is going to have on the way we work, live, and think. As someone who was there at the beginning, and has been Couch compliant almost since day one, I think these doubters need to step back and take a closer look at this technology.”
We feel there are mixed feelings amongst the Couch community about the current state of the automatically generated database URIs. To quote an example from one member; “I want to sit on the Couch faster, I don't want to type HTML in every time I feel like a REST.”
In this instance we feel the user is right, but we have come so far already? Can we really justify changing the URI scheme at this stage to a QuickCouch friendly version?
It has come to our attention that some people are taking advantage of the uncompiled nature of the Couch HTML source codes. We think a more secure method of Couching is needed, perhaps involving Cushion management, but it must be done without affecting the Open POUFFE Standards encouraged by Web 2.0.
We must face these challenges head on if we are to succeed in providing the next generation of Couch oportunities for the future of the web.