I think a lot of these early companies have high ambitions in terms of serving various languages, then they find out how hard writing SDKs and tooling for each of them is.
> ... they find out how hard writing SDKs and tooling for each of them is.
Absolutely. Each additional SDK adds a lot of maintenance effort. It isn't just a write-it-once thing:
- More time spent writing/updating docs
- More context switching in support channels
- More time spent updating SDKs as new features are developed
Staying focused on one SDK helps to keep velocity high in the early stages. But our product has matured enough that we feel comfortable gradually rolling out more language support, starting with Go soon
Absolutely. Each additional SDK adds a lot of maintenance effort. It isn't just a write-it-once thing: - More time spent writing/updating docs - More context switching in support channels - More time spent updating SDKs as new features are developed
Staying focused on one SDK helps to keep velocity high in the early stages. But our product has matured enough that we feel comfortable gradually rolling out more language support, starting with Go soon