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.
If seeing a word written down is traumatizing, you need more help, and you’re not suited for the professional world. If coddling people like that would make you select away from a project for something beyond its technical merit, then I question your ability act as a professional.
Building Gin: Simple over Easy
21–28 of 28 posts
Re: Building Gin: Simple over Easy
#22I'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.
Re: Building Gin: Simple over Easy
#23LLM tells: > 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,…
Re: Building Gin: Simple over Easy
#24LLM tells: > 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,…
thanks for the feedback! while i wrote all the story myself I let AI do a full rewrite, i have not developed the eye to do the editing yet
Re: Building Gin: Simple over Easy
#25The main reason we don’t use it anymore is that the default handlers don’t return the error type, which means error handling and HTTP status tracking get tricky and non-idiomatic as soon as your handlers start calling functions that can fail. It’s essentially a function coloring problem.
One could argue that HTTP status is a totally separate thing from normal errors, and I get that perspective, but that’s a significant ergonomic hit to take for the sake of philosophical purity.
Re: Building Gin: Simple over Easy
#26I 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!
Re: Building Gin: Simple over Easy
#27LLM tells: > 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,…
thanks for the feedback! while i wrote all the story myself I let AI do a full rewrite, i have not developed the eye to do the editing yet
Re: Building Gin: Simple over Easy
#28I'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 someone who has been sober for 10+ years and still avoids events where alcohol is served, the word Gin doesn't cause me any stress. Just one point of anecdata.