fuy

FWIW, I think they should've been much more open in their announcement and credited original teams instead of selling this as some kind of almost-autonomous Claude project.

"We took existing system we helped to implement at Meta and changed it a bit" doesn't sound as cool as "Redesigning source control at Anthropic", but seems to be closer to truth?

not necessarily, no. With SSDs you get much better IOPS for cold data, and many datasets fit in RAM. So a lot of (OLTP/HTAP) workloads can become CPU-bound due to sorting/hashing - bread and butter of joins.

yes, if you control the clients and do client-side pooling.

There's been many examples of societies where killing or abusing people was legal etc. Law is not math, it can be (and often is) wrong; in many cases a law is just a way for ruling class to make money/keep power etc. It's completely OK to protest laws, and it may be completely reasonable to consider someone a criminal even if they haven't broken any laws.

claude code easily uses 10+GB in single session :) 1Gb sounds very efficient by comparison

almost all Spotify playlists/radio features are extremely stupid. Radios all repeat the same 2-3 songs per artist, doesn't matter where you start. Classical pieces in radios are always 1-2 minutes long etc etc. It was like before AI though.

sorry about that, I appreciate the reminder. Sometimes it's hard to engage in conversations with obvious bots/bad actors in good faith.

CLUSTER command is not the same as index organized tables, it's a one-time "physical sort" operation. New data is not organized until you run CLUSTER again. Index organized tables are maintained automatically by Oracle/SQL Server.

Not saying you're wrong, but solo developers building (relatively) greenfield projects are the best bet for increased AI productivity.

Solo dev projects are usually reasonably sized (< million LOC), style is more uniform, there's fewer silos etc. etc.

Good studies look at a broader picture.

isn't this template supposed to mean that all the previous considerations are now obsolete?

It's web in a (limited) sense that there's probably a web frontend somewhere, but this "somewhere" is usually pretty far away from where most of the code is developed.

Most of the backend logic is not related to serving data for the browsers, it's doing actual backend stuff - communicating to databases, APIs, etc.

Is Google search backend a web app? I think it's really stretching the term.

Looking at first optimization, I wonder if double-checking after acquiring exclusive lock brings any performance benefits. The whole premise is that cache access is read-heavy, so not acquiring exclusive locks for reads eliminates by far the biggest problem.

Rare (I presume) cases of overlapping updates from different threads (considering updates themselves are also infrequent) don't seem like a big deal compared to lock elimination. Would be interesting to see benchmark numbers for those optimizations separately.