Friday, March 27, 2015


JSON  has now "officially" replaced XML as a communication format,
when one of co-authors of XML has prepared JSON RFC

ongoing by Tim Bray · RFC 7493: The I-JSON Message Format

The JavaScript Object Notation (JSON) Data Interchange Format
"JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data."

Tim Bray - Wikipedia, the free encyclopedia

ongoing by Tim Bray · XML’s 15th Birthday

It would be useful if binary version protocol (BSON) is also standardized,
or we should all just use Google's Protocol Buffers.

Comparing Protobuf, JSON, BSON, XML with .NET for File streams | Software Engineering
Protobuf is by far the best of all the serializers in terms of speed and size. If you require a readable format, depending on your requirements you can choose any of the other ones. If size is not important, the plain .NET XML serializer is the best after Protobuf."

Primer CSS (from GitHub)

Introducing Primer · @mdo
"Primer is GitHub’s internal CSS toolkit. It’s been the base coat for for years now, providing styles for our global typography, layout, tooltips, buttons, and more...

Primer isn’t another large front-end framework, though. It’s rather limited in functionality and isn’t intended to replace something like Bootstrap. It will always be GitHub’s internal toolkit first, designed to help build GitHubby things. That said, we love to share.

Primer is licensed MIT, so you can basically do whatever you like with the source code."

NoSQL performance: Couchbase vs. MongoDB

NoSQL Smackdown: Couchbase Dominates MongoDB in Benchmark Tests | Kurt Cagle | LinkedIn:

NoSQL showdown: MongoDB vs. Couchbase | InfoWorld

Couchbase Server - Wikipedia, the free encyclopedia

Couchbase is created a derivative of CouchDB, with intention to get high performance.

CouchDB is based on Erlang, so it is highly reliable, but Erlang is not optimal for handling strings and documents. So parts of the system ware moved to C, and later integrated with Memcached to get a high-performance system... With increased investments in "Big Data", NoSQL etc,

there is an increased competition...