gargantuan

Detailed release notes:

https://github.com/basho/riak/blob/riak-2.0.0/RELEASE-NOTES....

Goodies:

* CRDT : Convergent data types (counters, sets, maps)

* Strong Consistency

* Security Enhancements

BTW this is the author of Learn You Some Erlang for Great Good

http://learnyousomeerlang.com/

I just wanted to say that both this write-up and in the whole book you can see passion, and excitement for the topic. They say cliches like "work of love" but if anything that defines it I think.

It is the little humorous bits, the additional "Don't Drink Too Much Koolaid" parts, the visuals. It is a fantastic resource.

I think this post is a partially the response to "Why Cool Kids Don't Use Erlang" topic we discussed recently. There was a lot of "Too hard to get started" and I think Fred took the initiative and did something about it. That is great. Thank you Fred!

Also what about protocols? Can type systems handle that. Things like:

  * open file
  * close file
  * read form file

That can be type checked up and down it will still be broken. Is that Rich Hickey meant? Here we are dealing with a real world -- a file. And it has a protocol to access it. So in a sense we want a protocol checker not a type checker in that case...?

Good stuff.

* More work on the new web GUI

* Erlang 17.0 support. Presumably comes with better performance and concurrency handling (just from knowing what went into that release).

* Better performance for replication, especially handling large documents.

* Don't need write access to source db to replicate.

This is great. Really like working and developing with CouchDB. Well defined semantics and protocol of master to master replications really make this database unique. It might be a small thing for many but having a web GUI is another benefit. Can't tell you how many times I ended up looking in there to see what exactly has my code inserted into the DB.

Also looking forward for BigCouch merge in the near future.

> 2) Recursion & Tail Call Elimination: How would one solve this problem in any other language with a stack? Memory concerns don't just exist in the browser.

Be honest now, did you actually read the article ;-) because it answers that exact question.

---

> Languages with Tail Call Elimination will recognize this situation and basically rewrite the function into a while loop. Since this is a low-level function, we should do the same, but sometimes it's hard to know when you're recurring dangerously.

---

> but it won't go away just because you don't like it.

I didn't like it and it go away. Out came Dart. I like Dart. All worked out well so far.

Elixir has them built-in. They are basically an interface. A protocol says "this object implements this interface".

Get it at Erlang Solutions -- there are packages for Ubuntu, CentOS 6 and others.

> If you come from a static language background and you keep expecting a type-checker will save you from doing silly things like adding arrays to strings, you're always going to hate Javascript.

Hmm funny I come from a dynamic language background and never had a problem with the language telling me adding an empty list to an empty list should somehow be empty string. That is batshit crazy. Those are not silly things those are basic 101 strong type system checks that very dynamics languages like Ruby and Python can do.

Water and fuel supply lines as well along with transportation infrastructure.

kivy ? http://kivy.org/#home

I'll just file a patent on a business method profiting from patents on methods of organizing information.

> I always thought each spy dealt with very few handlers / I wouldn't have showed to a 'phone call'

Usually in these cases FBI and CIA would plant various stories in the media, and produce evidence during the trial that conceals real sources of information (often defectors and moles).

Otherwise, it seems like the alleged spies and their handlers were just very sloppy.