> Consider the actual cost of the thing long-term to your organization. A thousand times this. Not just in API versioning, but in everything. Every new thing

> Consider the actual cost of the thing long-term to your organization. A thousand times this. Not just in API versioning, but in everything. Every new thing you introduce is a thing you must first develop competency in, and then maintain competency in for the life of the project. This cost is paid during development, it's paid on every new hire onto that project, and it's paid on-going as you need to work with that tool and have your ops team deploy, manage, debug, and tune that tool (where applicable). Choose boring technology where possible if it's not directly related to your line of business.