Building a High-Performance OpenAPI Parser in Go(www.speakeasy.com)

16 pointsby subomi3 days ago2 comments

usrnman hour ago
> we process thousands of OpenAPI specifications every day
Doesn't really strike me as the load that requires writing a high-performance solution from scratch, especially on modern hardware.
- pseidemann11 minutes ago
  > Some were fast but modeled the spec loosely, making it hard to build correct tooling on top. Others were closer to the spec but used untyped maps everywhere, which made large refactors and static analysis painful.
  Correctness and types were the real reasons?
ryanackley2 hours ago
One observation I've had recently. Postman files seem more popular the OpenAPI specs lately. Major SaaS companies will produce a postman file but not an OpenAPI spec. Two examples: Salesforce and Notion
This is really unfortunate because Postman requires you to have an account and log in to download or export these to another format.
Prediction: Postman produces a paid MCP for API lookup in the near future
- throw-12-1616 minutes ago
  Postman is my goto example for saas enshitification.
  Something that should have just stayed foss.