riak-ruby-client wishlist

gistfile1.md

• ugh i hate beefcake
• maybe hate is too strong, but I don't like the way it's integrated
• beefcake feels unnecessarily divorced from the base protobuffs backend
• i don't enjoy copying message definitions
• scan riak_pb message definitions, build classes, provide a place for adding/overriding methods
• take all that http code and set it on fire for 2.0, burn it to the ground
• also the big-ass list of code to message names should be auto-generated or at least less shitty

• ugh i hate beefcake

Agree, least of all potential evils.

• maybe hate is too strong, but I don't like the way it's integrated

How would you change it?

• beefcake feels unnecessarily divorced from the base protobuffs backend

I initially had an intention to provide "native" backends in Cxx and Java, that got derailed. At least the encoding part did.

• i don't enjoy copying message definitions
• scan riak_pb message definitions, build classes, provide a place for adding/overriding methods

The proper place to do this would seem to be riak_pb. Let's make it into a gem.

• take all that http code and set it on fire for 2.0, burn it to the ground

+1000

• also the big-ass list of code to message names should be auto-generated or at least less shitty

This can also be part of riak_pb if you like. I want to get the python version of this over there but didn't manage to.

The proper place to do this would seem to be riak_pb. Let's make it into a gem.

Heh, I'm already planning this out in my noggin !!!