Building Gin: Simple over Easy

I released Gin in Hacker news more than 10 years ago! Changed my career and allowed me to meet a lot of interesting people. Thank you HN!

Related: Rich Hickey's 'Simple Made Easy' (2011) https://youtu.be/SxdOUGdseq4

Classic talk that still influences my design decisions today.

Thanks for the detailed walk-through @manucorporat . On designing for zero breaking changes, I see that is also a core value at Go. However, how did you actually apply it to software design and architecture? Got any resources to share here? Did you had to put more effort on other projects not running on Go to keep it also free from breaking changes?

I'm mainly building tooling in other runtimes like Rust and TS, and I'm interested to hear your take on it.

Cool! I used gin once on a company project.

I'm not sure if I could use a framework that shares the name with an alcoholic drink in a professional setting.

Plenty of people who struggle with alcohol and who would benefit of not being reminded of it at work too.

> You write the same plumbing for route params, request parsing, validation, and responses in handler after handler. None of it is hard. Enough of it becomes noise.

As a human, I would have written something like: > You write the same plumbing for route params, request parsing, validation, and responses in handler after handler. None of it is hard, but it makes the code noisy.

Whether or not an LLM wrote this, it's a writing style that sounds like a politician or a sophist, and it sucks.