proomt

Search

Search posts, papers, and topics

All posts

Google DevelopersAmir Hardon, Philipp Schmid3 min readintermediate

Why client SDK generation belongs in the open

Summary

Google partnered with Speakeasy to open‑source their OpenAPI‑based multi‑language SDK generator, covering Python, TypeScript, Go, Java, C#, PHP, and Ruby. The move replaces a now‑defunct proprietary generator, reduces maintenance overhead to ~1 engineer, and adds a CLI and documentation server generator under AGPLv3.

  • Closed‑source SDK generators pose platform risk; open tooling mitigates disruption.
  • Speakeasy’s generator produces idiomatic client libraries with static typing, SSE streaming, retries, and pagination across seven languages.
  • Open‑sourcing under AGPLv3 lets teams run the generator in CI while licensing generated SDKs as they wish.
  • Google’s migration reduced engineering effort from multiple engineers to roughly one, showing maintainability benefits.

Reliance on proprietary codegen can break developer pipelines when vendors disappear. Open, deterministic generators ensure continuity for fast‑moving APIs like Google’s GenAI services and enable broader ecosystem tooling (CLIs, MCP docs).

5/10

Related reading

  1. Article: Your Next DSL Author Is a Language Model

    Typed Domain Grounding (TDG) embeds a DSL inside a mainstream language the LLM already knows (e.g., Kotlin) and uses the host compiler as an oracle. The author describes five building blocks—embedding, choosing a host language with high training‑data frequency, compiler‑driven type safety, a generate‑compile‑repair loop, and an on‑demand teaching tool—and shows measured results from kUML, a Kotli…

    InfoQinfoq.com18 min
  2. A New Framework for Open Source AI

    Mozilla and partners published a paper proposing a layered, gradient openness framework for foundation models, defining openness for data, code, weights, docs, and deployment. The framework gives developers, regulators, and civil society a common language to evaluate openness and safety beyond a binary label.

    Mozilla Automation Teammozilla.org3 min
  3. I expected better from Google

    The authors of the open‑source project mobile‑use discovered that Google’s Artemis repository contains large blocks of identical Python code, examples, and even the same agent name without any attribution. They document the exact file diffs, the removal of their names via a force‑push, and the omission of their benchmark results from a public leaderboard. The post argues that this violates Apache…

    Lobstersminitap.ai6 minHN18032lobste.rs87