the_duke

I look forward to the second report from Jepsen for the new implementation then.

Brutal!

> ParticleDB 1.1.4 claimed to be a Postgres-compatible database ... Instead, we found a library of confusion

> exhibited frequent, profound transactional anomalies in essentially every way we could measure. We routinely observed the loss of committed writes, internal consistency violations, G1a (Aborted Read), G1b (Intermediate Read), and P4 (Lost Update). In the append workload, successfully appended values would routinely disappear from later reads of a given key. Our test suite inferred every kind of cyclic anomaly including G0, G1c, G-Single, and G2-item, but many of these can be attributed to more basic issues, like write loss. These issues occurred with a single server and without faults, and affected every transaction mode, interface, and WAL mode tested

To put things into perspective: Intel is still up 60+% (both year to date and over the last year), but down 45+% from the recent peak.

But there are very few small gasoline cars as well, even in Europe.

I guess the target market is small, otherwise more options would exist.

If you buy a car anyway, might as well pay a bit more and get one that is useful in more situations.

I adopted Copilot, Claude and Codex quickly, but I remained skeptical how far they would get us ... until the beginning of the year.

Then we saw the capabilities really take off, and it was obvious how things would go.

They want to IPO, so getting the revenue numbers up is probably more important than market penetration.

It used to be bad, but right now with the 200$ Claude sub I find it pretty hard to blow past the session limit.

You have to do a lot of things in parallel.

On r/codex the sentiment seems to be quite wide-spread.

The GPT 6 release was ... not great.

Sol 6 was so bad that I switched over to Opus 5.5 exclusively.

Huge regression compared to Sol 5.6, often doing really dumb things. Same for Luna.

Even Astra is very unreliable for coding. Brilliant for vision, sometimes just great, but it also often does very stupid things.

I'm a bit sour on OpenAI right now and skeptical that 6.1 will be much different.

(Note: this is after preferring and shilling Codex/OpenAI models for the last half year)

> Function return - what happened at tiananmen square?

Good one. Though this might unfairly bias against Chinese models?

Oracle also famously forbids posting public benchmarks of the DB.

Most of the Chinese models get into long complicated thinking loops before they accomplish something more complicated.

This is also true for Deepseek 4(.1) .

I disabled it once, it has always stayed disabled.

So it may or may not happen regularly, but I would not over-index on a sample size of one.