scraptor

Diversity win: this notation can't be easily understood by anyone!

The specific proposal is not great but changing the rules is in fact the correct solution of the current rules lead to systematically bad outcomes.

This time it has a major impact on the possible RNG outcomes even for a player who doesn't know about the bug, and it was caught much earlier in development before the permanent stability of existing seeds was guaranteed.

So what's your excuse for why New York has equally bad internet?

The idea was to transition from coal to natural gas while using solar and wind to reduce fuel consumption, thereby significantly reducing CO2 emissions. Any claims of hydrogen being burned were either lies to the public to get the gas plants built despite the non-green optics or lies to investors as part of a fraud scheme.

More efficient to spend the same amount of money on shoreside panels with lower installation costs.

Servers with ECC generally report zero recoverable memory errors until the chip starts failing, at which point there are increasingly many. Therefore the average server experiences zero cosmic ray related memory errors during its lifetime, despite having many times more memory than 256MB.

So how are the special interest groups keeping their enemies out?

The government will keep changing the rules until VW wins. Using tariffs, price floors, subsidies, whatever it takes.

This only applies to steam keys sold off site, which is why the original comment specified non-steam keys.

Interesting to see the definition of moat change from keeping other companies out to keeping your customers in.

I don't hate journald because it's not plaintext, I hate it because it's worse than plaintext. Somehow journald manages to provide a database which is 40x slower to query than running grep on a compressed text file. I'm all in favour of storing logs in an indexed structured format but journald ain't it.

sqlite resolves lock contention between processes with exponential backoff. When the WAL reaches 4MB it stops all writes while it gets compacted into the database. Once the compaction is over all the waiting processes probably have retry intervals in the hundred millisecond range, and as they exit they are immediately replaced with new processes with shorter initial retry intervals. I don't know enough queuing theory to state this nicely or prove it, but I imagine the tail latency for the existing processes goes up quickly as the throughput of new processes approaches the limit of the database.

But enough about trump, let's talk about iran