On Tue, Aug 26, 2014 at 2:23 PM, Nick Wellnhofer <[email protected]> wrote:
> Do you really want to complete the development of Python and Ruby bindings > first before telling people that they can start using Clownfish? Well yeah -- but if I haven't been persuasive enough, I'd rather go along with your plan. > At the current pace of development, this might take a couple of years. If I could work uninterrupted, Python and Ruby would probably take me a month each from where they are now. I guess that just means I have to work as hard as possible now to get stuff in before the concrete stiffens. And I have to be lucky about avoiding distractions. > What’s so bad about releasing new versions that break compatibility? I'm cool with it, I just think it's unrealistic. Once people start using the software, the social costs of breaking compat make it increasingly difficult to change things. Superficial changes which are nonetheless justified because they make APIs more consistent or simpler don't go over well with people who just want stuff to work and have to cope with disruption. Delaying API publication until as many known mistakes are ironed out as possible means less conflict and yields a better product. Marvin Humphrey
