Hacker News with Generative AI: API Design

Don't return named tuples in new APIs (snarky.ca)
In my opinion, you should only introduce a named tuple to your code when you're updating a preexisting API that was already returning a tuple or you are wrapping a tuple return value from another API.

API Design, Programming, Software Development

72 points by todsacerdoti 19 days ago | 66 comments

Ziggy: Data serialization language for expressing API messages, config files (ziggy-lang.io)

Data Serialization, Programming Languages, API Design, Configuration Files

104 points by thunderbong 46 days ago | 16 comments

Amazon APIs are the worst. No comparison. *Rant (ycombinator.com)
Working with amazon API's is single handedly the worst experience I have ever had programming. They are a textbook example of how to build the worst architecture, and their support system is designed to be almost unusable.

Programming, API Design, Customer Support

10 points by kderbyma 56 days ago | 3 comments

Design a GraphQL Schema – how to continuously evolve your schema (tailcall.run)

GraphQL, API Design, Software Development

12 points by amitksingh1490 119 days ago | 2 comments

Malloc() and free() are a bad API (2022) (foonathan.net)

Memory Management, Programming, API Design

49 points by davikr 130 days ago | 26 comments

The API database architecture – Stop writing HTTP-GET endpoints (fabianzeindl.com)

API Design, Databases, Software Architecture

93 points by fzeindl 195 days ago | 164 comments

TypeSpec: A new language for API-centric development (typespec.io)