@liw suppose not much actual discussion in the blog post?

1. could have a better model of how to use the library. Like having many usecases you see it in the context of you might notice if it falls short in any..

2. Could try change it _before_ (many)others use it. So fewer or no people are affected.

The first users might communicate issues that might need changes that affect upstream.

3. Can just make a v2 version and maintain both v1 and 2.. Now you can't do that for every little thing..

@liw Yes; I work with a migration compatibility stream that's always got to keep compatibility; the slightest change can have surprising incompatibilities. We often have to do bug-compatible things.

Sign in to participate in the conversation

Lars and friends