Andys

IIRC it came down to something crazy simple, like, using the FPU registers to bit-blit was the fastest way, but only on the genuine Intel Pentium.

I worked in a DC that had multiple redundant chillers on the roof, and multiple redundant coolers on each floor, but the whole building's cooling failed at once when the water lines failed somehow.

They didn't say how, but apparently the pipes between each floor and the roof were not redundant. It took almost 24 hours to fix.

Or..? A golden era for people who want to think of new things and test out their ideas quickly by having AI code it up.

Every piece of progress looks like this to begin with.

We did this at Chargify, but with MySQL. If Redis was unavailable, it would dump the job as a JSON blob to a mysql table. A cron job would periodically clean it out by re-enqueuing jobs, and it worked well.

This is made possible because Elastic gained a write-ahead log that actually syncs to disk after each write, like Postgres.

I came to a similar conclusion. What about measuring enjoyment? Turns out people enjoy meetings more than work!

I'm surprised that we're circling back to banning things being the answer, when we (the Internet) know that doesn't work long-term.

It seems nice at face value, so it appeases everyone, while being an overly blunt tool used as a political weapon, etc.

Imagine viewing the same chat logs, while logged in an admin interface, then it isn't self-XSS anymore.

What if you factored in time to sort them first?

Thanks for sharing that.

Presumably if you'd split the elements into 16 shares (one for each CPU), summed with 16 threads, and then summed the lot at the end, then random would be faster than sorted?