5 ms·
Ask HN: Creating SDKs for Multiple Languages?
Over the last week I was looking at nango.dev, and I think they have a great approach to integrations because there's not only a single API to all integrations but it's still highly customisable.
This felt perfect for our current use-case. So I wanted to use them right away. However, I couldn’t. They only support a Node SDK, and our entire backend is in Python.
This means working with REST APIs instead, which requires more effort such as doing REST calls, mapping the payload to the schema etc. It’s frustrating, because there seems to be this perfect solution that we just can’t use.
Is translating SDKs into a different language is a common challenge others face? And if so, how have you approached to solve this? Transpilation, LLMs, or manual rewrite?
For companies that provide SDKs in different languages, do you have an automated process for this, or is it still done manually?
- bosky101 2y agoThis launched recently here on showHN: https://sdk-fabric.org/ https://sdk-fabric.org/ comments at https://news.ycombinator.com/item?id=40416800 https://news.ycombinator.com/item?id=40416800
- yorwba 2y agoUse an OpenAPI spec to generate clients? Nango appears to have one https://github.com/NangoHQ/nango/blob/79545622929aa4c3dca94ffb2aa64468e00460ad/docs-v2/spec.yaml https://github.com/NangoHQ/nango/blob/79545622929aa4c3dca94f...
- sb13 2y agoYeah, that's an option. By the way, I've heard that the auto-generated code isn't that great to work with. Would you agree?