A high voltage DC line is being built to Singapore now from a solar generator in Northern Australia, so it's definitely doable to send over that distance (around 3,000mi).
I would like to see more storage though in its various forms; the oversupply is during peak daytime hours, however there's still large draw at night that could be offset.
You're right it is workload dependent. If you're low write but read heavy, you won't see huge differences in performance between RR and Serializable, so it can make sense to shift exclusively to that. The last benchmark here shows some of that with Postgres if you're looking for numbers (not an exhaustive test by any stretch): https://lchsk.com/benchmarking-concurrent-operations-in-post...
SQLite is single writer, so transaction isolation is easy, writes are linear by their very nature.
Cockroach does some really funky stuff, but its serialization guarantees are only within certain conditions. Traditionally it has also had low write throughput compared to other systems, mainly due to its distributed nature. Jepsen touches on that here https://jepsen.io/analyses/cockroachdb-beta-20160829 though things have vastly improved since then.
To your earlier point, it may not even matter depending on the workload, or if you're aware of your database limitations. In cases where it does matter then being aware of the limitations of something like Repeatable Read makes the trade-off worth it.
Potential timeouts for clients/workstations trying to reach microsoft.com.
Which entry is picked for use is generally random depending on the client.
Most systems will retry using another entry though on issues connecting through. That said, if you are on a network that is 192.168 based, trying to get to Microsoft.com may just send you to your local router!
Things is source code management these days even in mainframe but many shops still have you log into the same "box" to do your development. It can get pretty fun when trying to coordinate testing and patches.
> Things is source code management these days even in mainframe
Source code management on mainframes has been around for decades now. Pansophic started selling Panvalet in 1970, and Broadcom still sells CA-Panvalet.
Closer to RCS than to Git in feature set.
> but many shops still have you log into the same "box" to do your development
It is very common to have separate LPARs for production, test and development, even if all three are running on the same physical hardware - the isolation is strong enough that it is rare for something running in one LPAR to cause a problem in another.
The largest shops will have physically separate mainframes for production and non-production.
Completely forgot about this one, yet I spent so much time playing it! Absolutely true that pacing is key.
The version I had had cycle-based speed so it became unplayable when I changed computers for a faster clocked one, which prompted me to attempt coding a clone.
It's a fair question and certainly is possible to have firewalls on a per-server basis. We do that for incoming traffic primarily. The catch is if that server itself gets compromised then you can't count on those rules still being enforced.
Having dedicated network appliances acting as firewalls means from a security perspective you need to compromise the local machine and then also compromise a dedicated, hardened external system as well. It vastly ups the difficulty barrier.
This is an advertisement. "How to avoid SIM swapping? Get your provider to use a different authentication method (like this one!)".
In reality there is no great way to avoid it for services that have SMS as a fall back measure. Some phone companies allow a lock on transferring your SIM, requiring you to physically enter one of their stores in order to unlock, but that's about it.
I would like to see more storage though in its various forms; the oversupply is during peak daytime hours, however there's still large draw at night that could be offset.