2011-10-11, 22:08
Montellese Wrote:As you can see we already had to break backwards compatibility for all those namespaces just to get a clean API on which we can build in the future without having to break backwards compatibility again.
topfs2 Wrote:The API is far from backwards compat already in the move from v2 -> v4 (even if not great changes), thus we decided that we might aswell do ALL non-backwards compat changes which has bugged us. This to make less changes (perhaps even keep backwards compat) in the next upcomming versions.
EDIT: Also you all should consider v2 (dharma) to have been just a taste of whats to come, it was never really finished and was mostly added as a showcase. Eden (v4) is looking rather finished and polished. While we have lots of ideas for the future it is very cleaned out and should be maintainable.
Thanks for the feedback, guys.
I guess I should look at this as a blessing in disguise. It sounds like some of the things in the V2 JSONRPC APIs that have forced me to alternative APIs / methods (eg: HTTP-API) are being improved in the next release of the JSONRPC API.