Decompression during install is generally less of a bottleneck than network bandwidth, so fitgirl is doing it properly.

Here’s some that’s significantly cheaper than the graph would suggest: https://www.amazon.com/G-SKILL-Trident-64GB-SDRAM-Memory/dp/B0BSB94VC2

Not that it’s a good price in general or anything, but if you absolutely must buy now…

Get out

A bit hard to avoid when they play it in the theater. I mean I guess you can stand outside the theater and periodically poke your head in to try to guess if trailers are over.

I’ll consider myself lucky that the worst I’ve had to deal with was a 8K LOC C file that implemented image processing for a cancer detection algorithm. Nothing terribly tricky but just poorly organized. Almost no documentation at all. The only test was running this code against a data set of patient images and eyeballing the output. No version control other than cloning the project onto their NAS and naming it “v2” etc.

Research code can be really scary.

Hell I want it tattooed on me

The perch pose really makes it

Because finance in real life is not fun.

One Piece is best enjoyed as a manga. Reading it goes much faster and loses a bit of the anime character tropes.

Remember how you could play this on the local network with anyone who had a Nintendo DS? Only one person needed the game cartridge. So fucking cool.

You have no idea what you’re talking about. Stop spreading dangerous misinformation.

Honestly, delete this comment.

Ha. I’d expect nothing less from Theo.

Didn’t Firefox just release a new feature that prevents fingerprinting? Hard to get a reading on Mozilla these days.

My driving instructor said the airbag could rip the skin off your arms lol

I suspect every language does this to some extent. Some good examples from Japanese:

靴 = shoes 下 = under 靴下 = socks

手 = hand 紙 = paper 手紙 = letter

歯 = teeth 車 = wheel 歯車 = cog / gear

火 = fire 山 = mountain 火山 = volcano

Sadly (?) the Japanese compounds are often only compounds of the symbols, not the spoken words.

I think you’re right. An UPDATE would fail, but not an INSERT.

Skyrim came out 14 years ago.

I believe both SERIALIZABLE and REPEATABLE READ isolation levels would raise an error for this example.

And I looked this up: Postgres won’t retry the transaction for you either. Though ultimately I think this a good default behavior.

Sqlite does not have a SELECT ... FOR UPDATE feature. The alternative is BEGIN IMMEDIATE.

There is a subtle scenario with read-modify-write transactions in MVCC where SQLite lacks some grace (in my opinion).

In MVCC, transactions work with a point-in-time (read “between atomic transactions”) consistent “read snapshot” of the database.

Consider this example:

1. Transaction A begins and reads from table foo.
2. Transaction B begins and updates table foo.
3. Both transactions commit.

There is no conflict here because these transactions are isolated from each other via the snapshot mechanism. Transaction A’s read snapshot is immutable and will not see any writes from transaction B, even if they are happening concurrently.

Now what happens in this example (from the OP):

1. Transaction A begins and reads from table foo.
2. Transaction B begins and updates table foo.
3. Transaction B commits.
4. Transaction A tries to update foo.

This is a true conflict because both transactions are trying to write to foo, and transaction A’s writes might be based on what it just read. There is no consistent way for A to proceed, because B already wrote to foo, invalidating A’s read snapshot.

So SQLite handles this by returning an error to A, effectively requiring A to restart the transaction.

There are other ways this could be handled though. The DB could optimistically retry the transaction for you. There is even a special BEGIN IMMEDIATE; statement that it could use to proactively take a write lock on foo so that the transaction doesn’t get starved by other writers. But SQLite puts all of the responsibility on users to handle this.

I’m not an expert, so there could be a very good reason that SQLite works this way, but it feels a bit annoying as a user.

I don’t actually know off the top of my head how PostgresQL handles this particular scenario.