5,024 karma · joined January 3, 2013
1) fatalities have declined a lot from their pandemic peak. It looks kind of like a reversion to trend
2) exactly none of those fatalities were caused by a Waymo, because there has never been a Waymo fatality
https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/...
https://v11.rescript-lang.org/docs/manual/latest/migrate-to-...
"Anysphere runs pretty lean with around 150 employees and has a single digit monthly cash burn, a source tells me."
This is how we are doing it too, for the same reasons. For now, much easier to administer than trying to figure out who spends enough to get a real Claude Code seat. The other nice thing about using API keys is that you basically never hit rate limits.
https://github.com/helix-editor/helix/pulls?q=is%3Apr+is%3Ac...
1. While Helix dev is on the slow side, I think what you’re describing as specific to Helix is in fact the typical case in open source
2. In this case the author did a bunch of work up front and the maintainers said no almost immediately after the PR was posted
I agree they could be faster to say no, but I think part of it is that the maintainers would have to agree themselves and as far as I know they are not getting together to come to consensus about random Helix PRs every day.
https://github.com/helix-editor/helix/pull/12127#issuecommen...
It's rarely a good idea to do a bunch of work on a big change to an open source project in a direction that has not been validated by the maintainers. Or at least, if you do, do it for your own education and don't have high expectations that it will be merged. The contributor in question had a very good attitude about it.