Except there's no reason those things couldn't be supported in an existing API with less friction to adopt. It's software. I think the reason software abruptly

Except there's no reason those things couldn't be supported in an existing API with less friction to adopt. It's software. I think the reason software abruptly changes (API switches, rewrites, UX redesigns, etc) is because doing that employs more software people than incremental improvements to old stuff. I don't think this is necessarily a choice, it's just the way it works out. It's kind of a perfect business in that way. The downside is that occasionally an important customer says "enough!" They're totally justified in doing that, but it doesn't align with growth, so it's the cost of business.