I think the question is whether that's even relevant.

If AI becomes a commodity (will it?) you're better off being Google than OpenAI.

Microsoft struggled to keep up with the mobile industry frontier and here they are, healthier than ever.

I don't see how this will benefit the consumer, but I might be missing some second order effect?

And why do you think most people (and LLMs) just Google " reddit" ??

The project itself seems to be structued around 1.4k micro-crates[0] which I admit is a bit weird. Rust's compilation unit is the crate unlike C's per-file compilation unit, so if this was a 1:1 AI-assisted translation from the original Postgres source this might be an artifact of the translation.

[0] https://github.com/malisper/pgrust/blob/main/Cargo.toml

There might be some correlation here.

- Someone in the early 19th century

It's necessary that the defaults are secure. More so, not less, if the problem is hard.

Levenshtein distance is not only a well-understood problem, it's small, self-contained, and extremely well-represented in the training data. The kind of problem where even small/bad models can excel. The golden standard for those tasks is just "use a library" so no wonder the beefy models are expensive: you're chartering a commercial airplane to go grocery shopping.

My personal benchmarks are software engineering tasks (ideally spanning multiple packages in a monorepo) composed of many small decisions that, compounded, make or break the implementation and long-term maintainability.

There's where even frontier models struggle, which makes comparisons meaningful.

The inevitable "iron law of oligarchy".

https://en.wikipedia.org/wiki/Iron_law_of_oligarchy

I'm surprised you're surprised.

Giant corpos steal work from millions of independent artists and the State ruled that IP laws didn't apply to them, only to us common mortals.

My personal experience is that for production-grade code you need to steer the agent more often than not... so yes, at least some of us are watching the LLM code.

I mean: you still have the problem regardless of following HTTP verb semantics or not.

Don't do that, and you solved nothing.

Either I'm missing what you mean, or half the comments here are missing the point of idempotency.

Let's say your server received this request twice within one minute:

    {
      items: [ { id: 123, amount: 1 } ],
      creditCardInfo: { ... }
    }

There is simply no way to make the requests idempotent without an idempotency key. The only way to tell both situations apart is to key the requests by some UID. The HTTP verb is irrelevant.

Did I misunderstand what you meant?