eapache

3 ms·

1. 1.▲
   by eapache 7y ago

   For most published libraries every old version is always available and upgrading is never mandatory. For SaaS APIs the constraints of the business means that very few businesses (Stripe being the notable exception) want to support more than
2. 2.▲
   by eapache 7y ago

   My impression is that semver makes far more sense for published libraries (DLLs or ruby gems or npm packages etc) while date-based makes far more sense for SaaS APIs. The constraints and usage patterns are fairly different between the two.
3. 3.▲
   When is it wrong to click on a cow?(grandunifiedcrazy.com)

   1 points by eapache 7y ago|0 comments
4. 4.▲
   Show HN: Starscope – a better cscope for ruby and go(github.com)

   2 points by eapache 11y ago|0 comments