OpenAPI has flaws, so what?

Speakeasy's decision to utilize the widely adopted OpenAPI standard instead of creating a domain-specific language (DSL) has proven beneficial despite some complexities, as it allows for a better long-term developer experience through familiarity and a robust support ecosystem. Although OpenAPI's verbosity and limitations might seem like drawbacks, Speakeasy leverages vendor extensions to overcome these issues and enhance SDK generation without fully abandoning the standard. This approach not only mitigates concerns of vendor lock-in by providing enhanced code quality and coverage but also aligns with the broader developer community, encouraging the integration of their improvements into the OpenAPI standard itself. Speakeasy's strategy underscores the value of working within existing frameworks to improve and extend functionality, thereby maintaining compatibility and promoting collaboration, rather than attempting to replace a well-established standard with a new one.