Have the weak defaults that caused 91% data loss when recovering from network partitioning been fixed yet? http://aphyr.com/posts/285-call-me-maybe-riak
Last write wins is indeed a bad default for data integrity; I believe we received feedback early on from customers that siblings were too confusing for developers.
The good news is that Kyle was deliberately testing things that were effectively guaranteed to break, thus the high rate of data loss. Most applications won't be simultaneously writing the same keys on both sides of a network partition; there will typically be a healthier mix of new and old keys being written.