This is one of the reasons why we've created Jitar (https://jitar.dev). It moves all front/back communication from the code to the runtime, so integration is easy while maintaining end-to-end type-safety. Source: 12 months ago

Lots of these have been popping up lately, they all seem really good. https://buildwithfern.com/. - Source: Hacker News / about 1 month ago

Thank you for your encouraging words and insights! There are indeed popular DSLs and code to openapi solutions out there. Many of which are easy to plug in to the openapi-stack libraries btw! I guess I personally always found it frustrating to try to control the generated OpenAPI output using additional tooling and ended up preferring yaml + a visualisation tool as the api design workflow. (e.g. Swagger editor)... - Source: Hacker News / 8 months ago

Fern (YC W23) | Founding Engineer | New York City | $125k-$175k + equity | Full Time | Open Source | https://buildwithfern.com REST APIs underpin the internet but are still painful to work with. They are often untyped, unstandardized, and out-of-sync across multiple sources of truth. With Fern, we aim to bring great developer experiences to REST APIs. Our stack is Next.js +... - Source: Hacker News / 8 months ago

I think part of why tRPC shines is because it's tightly coupled to TypeScript (and especially Zod, its schema validation library of choice - many of its features map 1:1 onto TypeScript concepts that don't exist in many other languages), which means it can avoid many of the issues that OpenAPI generators have. I'd also like to see a good TS-first OpenAPI client - Fern [0] is probably the closest I've seen.... - Source: Hacker News / 10 months ago

For cross-language, I can recommend Fern, which works with OpenAPI http://buildwithfern.com. - Source: Hacker News / 10 months ago