3 ms·
Build libraries with a spec, encourage competing implementations. This is how it's been done for many years in Java land, and it's good; really good. But it do
by pron 13y ago
Build libraries with a spec, encourage competing implementations.
This is how it's been done for many years in Java land, and it's good; really good. But it does come at a price: change is much, much slower, and eventually people might get impatient and just do their own thing.
The way it works now in Java land, is that a new idea or technology comes along (e.g. web sockets), some projects implement it with no spec, and a couple of years later (hopefully; it sometimes takes much longer) a spec is created, and you get lots of compatible implementations.
Sometimes you want to pull your hair out in frustration at the pace, but sometimes you're so glad to have 4 or 5 high-quality implementations for a standardized API to choose from.
- janl 13y agoExcellent point! I think it is important to derive specs from working implementations and not the other way around ton begin with. But yes, once the spec is in place change gets harder. Bonus points for having a clear versioning / feature addition & deprecation strategy that allows quick development.