There were plenty of low level libraries available then, less in the way of frameworks. It was an environment that he was used to coding in and cross-platform (in the PC world anyway).
Given what it was in the very beginning versus what it very rapidly grew into, I guess it was just something that made sense at the time.
Likely the emarker chip in the cable is reporting higher power capabilities than the cable can support long term. It'll work initially but then can't maintain that after resistance in the wires increase with wear.
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.
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.
(The Thomas Covenant series was by Stephen Donaldson by the way)
Card definitely has his own style with his work. Whether it's great or not is dependant on the reader - http://one-starreviews.tumblr.com/ gives some fantastic examples.
If you can, try the Seventh Son series though. easier read than Speaker or Xenocide, and very interesting IMO.
It's an intriguing idea though if nothing else. A question here (I don't know your background if it's biology mind you): what actually happens in the metamorphosis between caterpillar and butterfly/moth or any larval animal for that matter?
It does seem rather radical to switch off a massive amount of genes and switch on a bunch of others in adulthood, drastically changing your physical form.
No trouble and agreed - rumours flying around like that don't help the problem. If there was that level of security breech, outsiders would probably do more than lock everybody out anyway.
Finding further information about it: looks like a core switch died with the backup not kicking in. 12 hours to work around is a but much though.
In IT security here in Melbourne, first I've heard of it. Also why would network security specialists need to fly over 30 hours from Europe? We also have some pretty capable teams on the ground here already.
Given the time frame of when it happened it's more likely a change that has been borked in some way with difficulties in rolling back.
Given what it was in the very beginning versus what it very rapidly grew into, I guess it was just something that made sense at the time.