Also the fact that they are applying this to the GitHub action they built, promoted, and directly integrated into claude code is pretty frustrating.

Seems a lot better than the other potential world we could lived in, where paths were a black box and every web server/framework invented their own structure for them.

I quite like pi and learned about the contribution guidelines a while after using it. Hard to complain about people making software for free using a process that works for them.

I will say having a project with a slim issue tracker that only contains things the maintainers have blessed (and thus presumably are more likely to get worked on) is pretty nice.

If you’re googling for a bug your hitting and come across and auto closed issue, you know you have to submit a higher quality issue to get it looked at, rather than just +1ing the existing lacking issue.

> Maintainers review auto-closed issues daily and reopen worthwhile ones. Issues that do not meet the quality bar below will not be reopened or receive a reply.

Seems like not an unreasonable way to deal with the problem of large numbers of low quality issues being submitted.

It is? If another company comes out with a better model tomorrow and offers it at the same price Anthropic charges for Opus, they’re going to lose customers fast. They have to keep training to keep selling inference.

Most businesses factor in the cost of making their product into the product’s P&L.

You think so? OpenClaw certainly owned the hype cycle for a while. There was a thread on HN last week where someone asked who was actually using it, and the comments were overwhelmingly "tried it, it was janky and I didn't have a good use case for it, so I turned it off." With a handful of people who seemed to have committed to it and had compelling use cases. Obviously anecdotal, but that has been the trend I've seen on conversations around it lately.

Also, the fact that the most starred repo on GitHub in a matter of a few months raises a few questions for me about what is actually driving that hype cycle. Seems hard to believe that is strictly organic.

One would hope Uber could manage 1 sentence API summaries (regardless of their quality) for less than $3.4 billion.

If you looked at https://asrs.arc.nasa.gov/ and thought, wow this webpage must 25 years old, you would be incorrect! In 2000, they had a very 1990s website with the option for a flash version and non-flash version: https://web.archive.org/web/20000407212204/http://asrs.arc.n...

The early versions of this design arrived in 2008, though it has a sweet sweet flash header complete with audio until 2021.

An even more irrelevant side note: it appears that archive.org has a javascript based flash emulator built in to run old flash websites, which is pretty amazing.

But in practice, it's basically impossible to use that way in conjunctions with workers, since you have to bind every database you want to use to the worker and binding a new database requires redeploying the worker.

Especially since you get all of the same advantages with plain old stream on consciousness commits and merges using:

git merge --no-ff

git log --first-parent

git bisect --first-parent

It’s basically always the bottleneck/problem source in a lot of systems.

My biggest complaint used to be that it would occasionally restart after a system update and I’d have to unlock FileVault in person, but macOS 26 now allows unlocks over ssh.

Extrapolating that out, the subscription pricing is HEAVILY subsidized. For similar work in Claude Code, I use a Pro plan for $20/month, and rarely bang up against the limits.

If you do it well, a startup can go through SOC2 and use it as an opportunity to put together a reasonable cybersecurity practice. Though, yeah, one does not actually beget the other, you can also very easily get a soc2 report with minimal findings with a really bad cybersecurity practice.

Or I am doing something so specific, that a local emulation of the aws api isn’t ever going to be good enough, so there’s not a lot of point in trying. For example, writing code that handles automatically spinning up RDS instances from an RDS snapshot — a local emulation of that process is going to be so far off from what would actually happen no matter what they do.

If I’m getting into esoteric features or some “big” features that don’t make sense locally, then I just spin up a real dev account of aws, so I know I’m getting the real experience.