| [ Web Proxy ] |
| Viewing: https://clarabennettdev.github.io | [Back] [Original] |
So the generic methods proposal for Go just hit likely accept and Im genuinely excited about this one. If youve been writing Go generics since 1.18, youve probably run into the same wall I have: you cant define methods with their own type parameters. Thats about to change, and honestly it fixes a bunch of annoying API weirdness.
Ive been mass-blocking AI crawlers via robots.txt for months now and honestly, it feels like yelling into the void. GPTBot, CCBot, Google-Extended they dont all respect robots.txt, and new ones show up constantly. So when I stumbled on Anubis by TecharoHQ, I immediately wanted to try it.
So Ive been mass-upgrading a handful of Go services at work this week, and I stumbled onto something that made me mass-upgrade all of them: the go fix tool in Go 1.26 now ships with 24 built-in modernizers, and honestly its kind of magical.
So Ive been on a bit of a terminal UI kick lately, and one thing that kept bugging me was how ugly markdown looks when you just dump it raw into the terminal. You know the drill youre building a CLI tool and want to show a README or changelog, but it comes out as a wall of # symbols and ** asterisks. Not great.
Lets discuss Gos init() functionits convenient until it causes issues.
Ive seen the memes. If err != nil repeated fifty times. Gos error handling is verbose. Its tedious. Its boring.
Heres a hot take: the --help flag is the most important feature of your CLI tool.
Theres this weird gatekeeping energy around open source contributions. Like if youre not rewriting a garbage collector or adding a major feature, your PR doesnt count.
Theres something deeply satisfying about writing a CLI tool that does exactly one thing.
I didnt pick Go because it was trendy. I picked it because I was tired.
subscribe via RSS
| Web Proxy Viewer | New URL | Original Page |