Am Sonntag, 8. März 2015, 10:20:17 schrieb xor: > I assume you made this suggestion of marking the new API unstable because: > 1) you then wouldn't have to wait for me to reply to your review results > 2) you didn't remember whether the review results contain any blocking issues > when you talked with Arne.
I made this suggestion, because this is a new API and you cannot know how people will use it. Predominantly synchronous usage could change what people need to use the API efficiently. Also an API which was mostly created by one person without any usage by third party implementors is almost by definition unstable. Or rather: It has to be open for change, because it is impossible to predict how people will use it. And being open for change without misleading early adopters of the API means marking it as unstable. Also it seems that you missed how stressful it was for Steve to review the API on the pretext of having to create a stable (=perfect) API. If you want the API to be perfect, then you will have to address every single worry someone has about the API. In a structure with such radically different budgets of development time as Freenet, this would likely be drawn out for months. So please mark it as unstable (for a few releases), so people know that the API is open for change in case real life usage shows up a need for that. In short: This has nothing to do with the quality of the code, but with community decision making processes Best wishes, Arne
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
