seems to me like Erlang is a selling point for some folks. The
sentence reads as if the project is apologizing for it's use of
Erlang. The key point is the use of HTTP so perhaps the mention in
that sentence of Erlang ought to be dropped entirely:
As the API is REST-ful any client environment that supports HTTP can
access a CouchDB database. The database engine is implemented in
Erlang, a highly robust scalable functional programming language ideal
for building distributed systems. The use of Erlang has made for a
simple yet flexible design that is readily extensible and easily
integrates with other server processes.
On Jul 26, 2009, at 11:24 PM, Curt Arnold wrote:
On Jul 26, 2009, at 9:03 PM, Nicholas Orr wrote:
On Mon, Jul 27, 2009 at 8:47 AM, Noah Slater <[email protected]>
wrote:
Apache CouchDB is a document-oriented database with a RESTful JSON
API. It
provides incremental replication with bi-directional conflict
resolution,
and
can be queried and indexed with JavaScript, or any other language.
CouchDB is written in Erlang, but can be accessed from any
environment
that
allows HTTP requests. There are myriad third-party client
libraries that
make
this even easier from your programming language of choice.
I'd suggest removing the word "but" and make it "and":
CouchDB is written in Erlang, and can be accessed from any
environment that
It's one of those brain/language things everything before the word
"but" is
invalidated by the presence of "but".
"I would go, but I have something else to do..."
Nick :)
The intention of the sentence is that potential users should not be
discouraged from using CouchDB due to its implementation language.
Using "and" loses that sense. Perhaps:
Though CouchDB is written in Erlang, it can be accessed from any
environment that allows HTTP requests.
