I look forward to the next API revision. Churning your API frequently turns me off as a developer who would rather not be deprecated out the gate.
This is how software improves. You are not forced to upgrade to the next version.
Improvement or not, to buy into a product that has churned twice in one year is a bad investment and for those who are lucky enough to not be caught in the middle - should be warned.
edit: I've used V4 and it's a vast improvement, but I stand by my remark.
That was 2 years with only one breaking change.
2.0 -> 3.0 removed deprecated 1.0 API, fully BC with 2.0
The only churn is for people who don't stick to stable releases, and that's their own problem.
v3.0.0-alpha.1 released this on May 19, 2016
v3.0.0-alpha.3 released this on Aug 2, 201
v3.0.0-beta.1 released this on Sep 16, 2016
v4.0.0-0 released this on Sep 13, 2016
v3.0.0 released this on Oct 24, 2016
> ... and that's their own problem.
Hence deprecation right out the gate. V4 is much better, great work - but blaming users for API churn does not make me confident. Sure users could have used a stable release, but then upgrade twice? What confidence is there that it won't churn again?