Client API philosophy

2014-11-09 Thread Christopher James Halse Rogers
Hey all. We're getting into the meaty bit of client API support I thought I'd write some things about API design philosophy to see if they're controversial. *) An API with lots of functions that do one thing each is simpler than an API with few functions that do different things depending on

Re: Client API philosophy

2014-11-09 Thread Daniel van Vugt
Definitely controversial; factually false or easily arguable. Sounds like a response to one of my merge proposals. So please put arguments in the code reviews... On 10/11/14 10:48, Christopher James Halse Rogers wrote: Hey all. We're getting into the meaty bit of client API support I though

Re: Client API philosophy

2014-11-09 Thread Daniel van Vugt
BTW, I do actually agree with half of your points. Just feel that over-generalising in a discussion like this one is counter-productive. Because it always is (<- over-generalisation). On 10/11/14 11:31, Daniel van Vugt wrote: Definitely controversial; factually false or easily arguable. Soun

Re: Client API philosophy

2014-11-09 Thread Christopher James Halse Rogers
On Mon, Nov 10, 2014 at 2:31 PM, Daniel van Vugt wrote: Definitely controversial; factually false or easily arguable. Sounds like a response to one of my merge proposals. So please put arguments in the code reviews... It indirectly is, but also in response to some discussion on IRC of one o

Re: Client API philosophy

2014-11-09 Thread Daniel van Vugt
We frequently disagree on the measurement criteria :) Also, IMHO code reviews provide a more structured place for targeted discussions. And that helps to focus on facts, with less hand-waiving. On 10/11/14 12:10, Christopher James Halse Rogers wrote: On Mon, Nov 10, 2014 at 2:31 PM, Daniel v