4 ms·

oapi-codegen looks pretty cool (it seems I starred it some time ago) but for starters, it's Go only. Stainless does a bunch of languages with more on the way.

oapi-codegen looks pretty cool (it seems I starred it some time ago) but for starters, it's Go only. Stainless does a bunch of languages with more on the way. You can see an example of the Go code Stainless produces here: https://github.com/cloudflare/cloudflare-go https://github.com/cloudflare/cloudflare-go (I'm the Stainless founder)

itslennysfault 2y ago
That one only does Go, but it is just one of many OpenAPI generators. I used openapi-generator and was able to produce SDKs for TypeScript (angular and node), Dart (Flutter), Kotlin (andoird), and Swift (iOS). They worked great for our purposes and I really had no complaints or issues. I guess my question is, what is the key differentiator that Stainless offers above just using OpenAPI and its huge library of existing generators? https://github.com/OpenAPITools/openapi-generator https://github.com/OpenAPITools/openapi-generator
- rattray 2y ago
  If it works great for you, that's great – stick with it! From what I've seen, a lot of API developers find that openapi-generator flat-out breaks or produces broken code for their OpenAPI spec (varies language-to-language of course). Beyond hitting the "it just works" mark more often, some other key differentiators: 1. much easier to configure & customize 2. auto-retry with exponential backoff (this is huge for our customers) 3. auto-pagination 4. overall ergonomics of using the SDK 5. internals that look handwritten (some people care, others don't) 6. one-click releases to github & package managers w/ semver, changelogs, etc 7. careful handling of edge cases (eg, will adding a new enum variant cause your Java client to crash?) 8. a long tail of more advanced features, like webhook signature verification, streaming, etc Thanks for the question – hope this helps :)
  - itslennysfault 2y ago
    Very helpful. Thanks for the details.

itslennysfault 2y ago

That one only does Go, but it is just one of many OpenAPI generators. I used openapi-generator and was able to produce SDKs for TypeScript (angular and node), Dart (Flutter), Kotlin (andoird), and Swift (iOS). They worked great for our purposes and I really had no complaints or issues. I guess my question is, what is the key differentiator that Stainless offers above just using OpenAPI and its huge library of existing generators? https://github.com/OpenAPITools/openapi-generator https://github.com/OpenAPITools/openapi-generator

rattray 2y ago
If it works great for you, that's great – stick with it! From what I've seen, a lot of API developers find that openapi-generator flat-out breaks or produces broken code for their OpenAPI spec (varies language-to-language of course). Beyond hitting the "it just works" mark more often, some other key differentiators: 1. much easier to configure & customize 2. auto-retry with exponential backoff (this is huge for our customers) 3. auto-pagination 4. overall ergonomics of using the SDK 5. internals that look handwritten (some people care, others don't) 6. one-click releases to github & package managers w/ semver, changelogs, etc 7. careful handling of edge cases (eg, will adding a new enum variant cause your Java client to crash?) 8. a long tail of more advanced features, like webhook signature verification, streaming, etc Thanks for the question – hope this helps :)
- itslennysfault 2y ago
  Very helpful. Thanks for the details.