11–20 of 28 posts
I'm mainly building tooling in other runtimes like Rust and TS, and I'm interested to hear your take on it.
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.
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.
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!
Great to see you here :D
> 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…
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.
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.
Truth be told, I came up with this name when I was 12 years younger. The other big framework back then was called Martini. And Gin pretended to be the idiomatic version for Go. Go -> Gin
Classic talk that still influences my design decisions today.
> Fyve faded. Gin kept going.
> the honest version of web programming: no magic, explicit control flow, and a handler shape you can hold in your head.
> keep the request path explicit, run no reflection there, and put the boring work behind one object you can inspect: the Context.
> None of it is hard. Enough of it becomes noise.
> we didn’t rename ours — we made gin.Context satisfy the standard interface, adding full compatibility
> Params land in a small slice, the matched handler is already sitting on the final node, and the request path avoids reflection.
LLMs tend to write in this style full of short sentences or phrases separated by commas.
It's actually hard to understand what the point is at times:
> The work follows the length of the URL, not the number of routes registered in the app.
> That is the kind of performance work I trust: fewer operations on the hot path, and fewer concepts in the programmer’s head.
> The quiet goal was zero breaking changes.
Adjectives such as "honest" and "quiet" are LLM tells.
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.