Readit News logoReadit News
simplesager commented on The Stainless SDK Generator   stainlessapi.com/blog/ann... · Posted by u/brandur
lapusta · a year ago
We've recently evaluated all four platforms—Stainless, Fern, Speakeasy, and Liblab—and here are our key takeaways:

Stainless: The standout for maturity and idiomatic code generation. While method signatures across products may look the same, Stainless shines during developing & debugging - making their codebase easier to navigate. They have a practical separation of SDK configuration from OpenAPI specification, setting it apart from others reliant on OpenAPI overlays. The Stainless Studio also proved invaluable for refining our OpenAPI specs during our exploration phase.

Fern: Notable for being open-source, though not free. It provides a robust end-to-end Developer Experience, covering everything from SDKs and documentation to Postman collections. Fern uses an internal "Fern Definition" language (~ think Smithy), it's optional and enables capabilities like merging multiple specs, but is adding another layer to navigate in our view.

Speakeasy: Moves at a fast pace, which could be a double-edged sword. Rapid iterations may lead to frequent, potentially disruptive updates for customers. A minor gripe was the inclusion of "Speakeasy" in class names, which felt overly branded.

Liblab: Initially limited in language support, they've expanded but still lag behind in establishing a strong customer base, which might be a red flag for some adopters.

BTW all folks are very approachable and collaborative!

simplesager · a year ago
Thanks for the mention! We do move fast and to help manage the changes better we've introduced a number of change management concepts recently like breaking change detection and more controls around semver. The updates can also be stacked by the user into PRs and versions updated and published in one go. Definitely choices that we can guide you through

On the Speakeasy branded classes. We got rid of that some time ago based on customer feedback. Check out our new TS generator https://www.speakeasyapi.dev/post/how-we-built-universal-ts

simplesager commented on The Stainless SDK Generator   stainlessapi.com/blog/ann... · Posted by u/brandur
simplesager · a year ago
Congratulations to the Stainless team on a fantastic launch! I'm one of the co founders of Speakeasy (https://www.speakeasyapi.dev/). We do similar things in the SDK space and some other things too.

I resonate with a lot of what is said in the comments. Last mile API tooling is underrated and most companies don't have the deep API platform expertise to build from scratch. The OSS options in the space proved SDK generation could be done but the actual product that you got in hand still needed a lot of work to be enterprise ready. The code was poor quality, wasn't customisable and there was no change management story. We're seeing a new wave of work in this space that's making api platform engineering much more accessible.

The API devex story starts with SDK creation and maintenance but there is a lot more to come!

simplesager commented on Ask HN: Who is hiring? (April 2024)    · Posted by u/whoishiring
simplesager · a year ago
Speakeasy (https://www.speakeasyapi.dev/) | Product Engineers (Full Stack), Founding Designer, Developer Advocate | US (SF), London (UK) | Full Time (Open to Remote, with willingness to travel a few times per quarter)

Hey there ! I'm Sagar, one of the co-founders at Speakeasy. We build tools to enhance the API developer experience. This primarily includes production-quality automatically-generated interfaces for companies' APIs such as SDKs and Terraform providers. Our mission is to assist teams in distributing their APIs to developers while handling the complex aspects.

We're a small, highly autonomous team looking for contributors to drive major projects from inception through delivery and iteration, working closely with our customers and community. If you're interested in developer-focused UX building with code generation, linters, parsers, LLMs you might find our work engaging. Although our primary languages are TypeScript and GoLang, our code gen product spans across more than eight languages — we're truly polyglots! As we scale rapidly alongside our customers, we're eager for individuals excited about delivering products that could impact millions of developers. Learn more about our "why" here: https://www.speakeasyapi.dev/docs/introduction/api-devex

Apply here https://jobs.ashbyhq.com/Speakeasy or email me at sagar@speakeasyapi.dev

simplesager commented on Show HN: Auto-generate an OpenAPI spec by listening to localhost   github.com/Adawg4/openapi... · Posted by u/adawg4
ivan888 · a year ago
I think going from code to OpenAPI makes a lot more sense, at least for strong typed languages. And even if not directly translated from code, at least closer to the actual code, in annotations or something. Generating the spec from code removes a step, where you simply need to update code, rather than update the spec then update the code
simplesager · a year ago
Completely agree. Keeping the openapi spec as tightly coupled to types in code builds a single source truth from your development to your deployment
simplesager commented on Ask HN: Who is hiring? (December 2023)    · Posted by u/whoishiring
simplesager · 2 years ago
Speakeasy (https://www.speakeasyapi.dev/) | Senior Product Engineers (Fullstack) | US (SF), London (UK) | Full time . (Will consider Remote too if you are open to travel a couple times a quarter).

About us: Hey there ! I'm one of the co founders of Speakeasy. We're building out a complete toolchain for API developer experience starting with production quality interfaces for company's APIs like SDKs, terraform providers and other novel generation targets. We help teams distribute their API to developers and deal with all the tough bits of scaling API usage.

You'll own, drive on major projects from inception to delivery and iteration with with our customers and community. You'll enjoy working on the stack if you're interested in codegen, linters, parsers, llms and developer focused UX. Our primary languages are Typescript and Golang but being a codegen product we work across 8+ languages, we're polyglots! We're scaling quickly with customers and looking for folks who are excited by the idea of shipping products that can touch millions of devs. More on the "why" here: https://www.speakeasyapi.dev/docs/intro

We're a small but tight knit team that iterates rapidly on product and has high autonomy to drive the business forward.

Apply here https://jobs.ashbyhq.com/Speakeasy or email me at sagar@speakeasyapi.dev

simplesager commented on How to wrap your Terraform Provider for Pulumi   speakeasyapi.dev/post/pul... · Posted by u/simplesager
simplesager · 2 years ago
Its a spicy time in IAC. Here is quick guide on how to leverage your existing terraform provider to unlock the Pulumi ecosystem using the Terraform Bridge.
simplesager commented on OpenAPI v4 (aka Moonwalk) Proposal   github.com/OAI/moonwalk... · Posted by u/mooreds
mbell · 2 years ago
I've tried using OpenAPI a few times, it's been...lackluster... I probably won't use it again.

Here are my gripes:

1) For me one of the biggest selling points is client code gen (https://github.com/OpenAPITools/openapi-generator). Basically it sucks, or at least it sucks in enough languages to spoil it. The value prop here is define the API once, code gen the client for Ruby, Python and Scala (or insert your languages here). Often there are a half dozen clients for each language, often they are simply broken (the generated code just straight up doesn't compile). Of the ones that do work, you get random PRs accepted that impose a completely different ideological approach to how the client works. It really seems like any PR is accepted with no overarching guidance.

2) JSONSchema is too limited. We use it for a lot of things, but it just makes some things incredibly hard. This is compounded by the seemingly limitless number of version or drafts of the spec. If your goal is interop, which it probably is if you are using JSON, you have to go our and research what the lower common denominator draft spec JSONSchema support is for the various languages you want to use and limit yourself to that (probably draft 4, or draft 7).

On the pros side:

It does make pretty docs - kinda wish it would just focus on this and in the process not be as strict, I think it would be a better project.

simplesager · 2 years ago
I'm working on a company https://speakeasyapi.dev/ with the goal of helping companies in this ecosystem get great production quality client sdks, terraform providers, cli(s) and all the developer surfaces you may want supported for our API. We also manage the spec and publishing workflow for you so all you have to do is build your API and we'll do the rest.

Feel free to email me at sagar@speakeasyapi.dev or join our slack (https://join.slack.com/t/speakeasy-dev/shared_invite/zt-1cwb...) . We're in open beta and working with a few great companies already and we'd be happy for you to try out the platform for free!

simplesager commented on OpenAPI Generator allows generation of API client libraries from OpenAPI Specs   github.com/OpenAPITools/o... · Posted by u/mooreds
PebblesHD · 3 years ago
Great to see other engineers focusing on this space. I’ve spent a good chunk of my career writing in-house clients for various business critical APIs and have always had a giggle that our self-made ones were often far nicer to use than anything on the market but was always disappointed that due to a variety of corporate constraints they will never see the light of day. I can see a big benefit to bespoke hand-rolled clients with a solid developer experience so keen to see where you guys go!
simplesager · 3 years ago
Thanks ! let us know if you'd want to try it out, happy to give you early access or generate a few SDKs for you.

u/simplesager

KarmaCake day45May 6, 2022View Original