From 3157ab8f2e5e28df80cb2991e9e70c828d918df8 Mon Sep 17 00:00:00 2001 From: Aaron Boodman Date: Thu, 21 Sep 2017 00:01:26 -0700 Subject: [PATCH] Update README.md --- README.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/README.md b/README.md index bb0f874983..0fe30ff3a9 100644 --- a/README.md +++ b/README.md @@ -28,13 +28,11 @@ Finally, because Noms is content-addressed, it yields a very pleasant programmin Working with Noms is ***declarative***. You don't `INSERT` new data, `UPDATE` existing data, or `DELETE` old data. You simply *declare* what the data ought to be right now. If you commit the same data twice, it will be deduplicated because of content-addressing. If you commit _almost_ the same data, only the part that is different will be written. -
- ## Use Cases ### [DecentDB](./doc/decent/about.md) - A pretty good database for the decentralized web ### -Because Noms is very good at sync, it makes a great basis for rich, collaborative, fully-decentralized applications. +Because Noms is very good at sync, it makes a decent basis for rich, collaborative, fully-decentralized applications. ### [BucketDB](./doc/olap/about.md) - Horizontally scalable OLAP database in an S3 bucket ### @@ -44,8 +42,6 @@ The immutable and content-addressable design of Noms makes it possible to build Embed Noms into mobile applications, making it easier to build offline-first, fully synchronizing mobile applications. -
- ## Setup ``` @@ -56,8 +52,6 @@ go get github.com/attic-labs/noms/cmd/noms go install github.com/attic-labs/noms/cmd/noms ``` -
- ## Run Import some data: