HN in general gets ahead of its skis a ton on legal stuff, it’s not personal. I deserve what I’ll get for speaking plainly to you, I hope the fact I’m speaking plainly and incurring cost will encourage you to move slightly more slowly.

In order:

Regulating interstate commerce is a fed thing, yes, that doesn’t mean states are unable to do anything at all to companies operating in multiple states. It was jarring to hear that described as one of the most settled principles we have.

NYS was not asking for a national TRO. It was jarring to read that asserted.

The first paragraph of the CFTC release we are commenting on says it ordered Kalshi to be able operate nationally. It was jarring to read it was made up that the CFTC ordered it to be able to operate.

5,940 commits, one author, 29 days. 5,067 of them, 85%, have a `Co-Authored-By: Claude` trailer. Busiest day is 1,393 commits, running 60-105/hour for ~20 hours straight. Commit messages reference .claude/skills/fleet/ and agent worktree "lanes". That's an unattended agent fleet committing once a minute around the clock. Commit count used to mean review time. Here it means GPU time.

Also: the v0.2 tag shares no common ancestor with main. git merge-base fails. "The actual git history" is an orphan branch grafted in after the fact.

And the testing rigor we're crediting them for should be weighed against the headline claim: 300x faster than Postgres, ahead of ClickHouse: fastest analytical DB on earth, one guy, one month.

Most damning: the Postgres baseline ran with *max_parallel_workers_per_gather = 0*. Parallel engine vs. deliberately-hobbled single-core Postgres, headline says 300x.

Using AI is fine. But "look how many commits" is precisely the signal this workflow is built to fake.

2.

Commit #1's message is "hey claude, do a breakthrough" from a week ago and is 1.5M lines. Commit #2 is "blog post" from 4 days ago.

My head is spinning. I don't mind AI stuff or AI enabled stuff but there's gotta be some bar for ending up on HN, and also personal accountability: the lack of humility and honesty sets a new low for me. There is no "we" who "released pgrust 0.2". It's one person cosplaying a serious engineering team doing a mountain of work. The bus factor is 1, and its one you can't trust on the basics.

ex. the first 1/3 of the blog post is bloviating about how a rust for loop is faster at summing 500M numbers on the heap than loading the numbers from a table and summing them.

It leaves me in quite some anguish. This site kept me well-informed and growing for 16 years. It is no longer reliable for that as long as things like this can be the #1 post with 60 comments, with the author here, and no one mentioned any of this.

Is this criteria satisfied if we swap the titular “AI” with our inoffensive “automating the voice”?

Generally, it is not young web devs fault that SwiftUI exists, and certainly not their fault it still has serious issues 7 years in. The things named in the article as not-working in SwiftUI do work in fine in the others.

It’s easy to say they were just trying to be trendy and thus the real flaw was the trend is bad and the fault of worse devs than us (the young web devs mentioned)

The thing that obviates that is the trendy stuff works, yet, SwiftUI doesn’t.

(source: I wrote ObjC/Cocoa as early as 2006, and switched to Flutter as my primary dev kit some years ago: it simply doesn’t have the performance issues mentioned.)

- Post a few up is way too aggressive about completely dismissing Iran conflict inflation/gas. It matters, big time, and specifically for Japan, it's a 3rd thing to add to above external sources of inflation.

- They held interest rates while ex. US hiked them, also making currency less valuable. (intentionally, and a good idea)

FWIW this isn't necessarily a bad thing, for Japan. It broke the dam of stagnation.

It is more unusual that the US did this than that Japan's currency depreciated.

My $0.02: the backstory starts with the bonds boys not liking the new fed chair. Long term USD interest rates spiked big time this week, after his press conference, not after the announcing they weren't hiking rates.

If they allow another spike due to dread of Japan dumping Treasuries, you might suddenly have a crisis

(your source: 38 yo, BA in economics @ 22, who kept up with economics nerdery along the years)