I took a look at the project and it was a 100k+ LoC vibe-coded repository. The project itself looked good, but it seemed quite excessive in terms of what it was solving. It made me think, I wonder if this exists because it is explicitly needed, or simply because it is so easy for it to exist?

“Walk. 43 meters is basically crossing a parking lot. ”

I wonder what will happen with new LLMs that contain all of these in their training data.

Personally I find that sticking to distros backed by companies or very large communities is just easier in the long term (Debian/Ubuntu/Fedora/Arch).

[1] https://news.ycombinator.com/item?id=46092225

Interestingly, since we are talking about Go specifically, I never found that I was spending too much typing... types. Obviously more than with a Python script, but never at a level where I would consider it a problem. And now with newer Python projects using type annotations, the difference got smaller.

The state however is always stored in a _separate AWS account_ that only the devops team can manage. I find this to be a reasonable way of working with TF. I agree that it is confusing though, because one is using $PROVIDER to both create things and manage those things at the same time, but conceptually from TF’s perspective they are very different things.