The problems start when there is a lot of changes on one branch and usually the first band-aid is to put a commit queue in place. The few very big companies that need even more than that probably aren't going to put their code on a new git hosting provider tomorrow.

I still remember that they launched GitHub Actions in 2018 and back then I was thinking: They can't even make the website reliable, surely this will only cause them more problems.

So you can bring your agents to any remote system, it even works somewhat well for network devices.

How does that work? To me it sounds like there is an enormous risk that they get regulated to death. They can't sell their product.

I have to use Gmail at work and it is just terrible.

Unless you have millions of users, you don't really need this. It would be nice to have but its not a pressing need. So why invest into developing something that you only need once you are at massive scale? At this point you might as well switch away from Postgres because you'll surely have the manpower to do it.

Even with a proxy like PgDog the Postgres sharding story isn't solved. Resharding with logical replication is unlikely to work with databases which are already TBs in size. I never got it to catch up, I had to sync data at the filesystem level which is terrible. Tools like pg_repack also fall apart at scale.

For those that get to a point where a sharding proxy is required, switching databases is a very appealing solution.

And for those that are almost there, application side sharding is more flexible than building a query routing proxy.

It is obvious to me that this will be used in performance reviews in the future.

You can't tell me that this wasn't known by Apple before shipping the product. Why did they not provide adequate cooling for the CPU?

If you add raw=1 to the URL then it will directly show in the browser without the Dropbox viewer.

Or did you share a folder?

The map is 30Mx30M blocks so outside of the very center you'll not see that much player activity.

DonutSMP is the largest Minecraft server today, the overworld is 225,000x225,000 blocks and the map is modified wherever you look.

The release will have an .sfv file with a CRC32 checksum for each rar file.

The FTP server checks them after the upload completes. Back in the day glftpd with zipscript was a very popular tool to manage an FTP site. This Readme sums it up well: https://github.com/pzs-ng/pzs-ng

The sfv can be tampered with but the propagation of releases to FTPs happens very fast, within minutes. It would take you longer to meaningfully alter it than it takes the racers to distribute the original files. And once the release is completely uploaded you can't modify the files anymore.

If the release is bad, for example if it doesn't work at all or if it contains a virus, then it simply gets nuked. This propagates within minutes.

Some was stored underground in the past with bad results because the former mines were unstable.

https://en.wikipedia.org/wiki/Asse_II_mine

https://en.wikipedia.org/wiki/Morsleben_radioactive_waste_re...