... And if the systems you actually interact with go down, you can get fucked as well.
If you want to buy food with Monero and the payment processor for the local shop doesn't work, even if it's a local machine sitting in the back office, you still can't buy anything.
Bitcoin lightning is absolutely hilarious. Your solution to Bitcoins problems is - not using Bitcoin. Wow, galaxy brain move.
The energy cost to maintain the base chain is <1% of global energy use, mostly from renewables
Yeah, that's bullshit. First of all, 1% of energy use for a network that serves a few million transactions per day is really bad. A single 1kW node in Visa's datacenter churns through that in an hour.
Second, it's not renewables. It's everything they can get for cheap. And that's often enough coal, gas, oil. Also, they're driving up power demand as a whole, which means fossil energy is actually needed longer.
That's decades of legacy for you...
I bet each step/arrow/decision had a good reason at some point, but most of them probably back when computers lived in caves and hunted their tapes using spears and rocks.
I feel like we're slowly reaching a point where the complexity is collapsing in on itself - just look at the absolute chaos a modern web app is.
That's the point.
In Germany there was a battle between left and right back then. The economy boomed in the 20s and faltered in the 30s. Capitalists saw the threat of socialism looming just behind Poland and so they supported fascism.
The Nazis funneled billions into large businesses. It was unsustainable and morally multi-level wrong, but they skimmed a lot of profits from these agreements. They got rich, while the economy started to collapse - even before the war.
Even after the war, most of them got away. They kept much of their wealth.
Prudes....
Java's Duke just stands there, fully nude and is giving NullPointerException fucks.
Stupid idea. Obviously 8 data laptops and one clock laptop would be the better solution. Parallel interfaces are inherently superior.
Glad that he's taken advantage of.
Yeah, but number go up!
Or requires a timestamp with zone offset, but ignores the zone offset, so you have to send the timestamp itself with a zone offset of zero relative to the systems timezone, but can't just omit the zone offset, because it's required.
Again, did you actually read the comments?
Is SQL an API contract using JSON? I hardly think so.
Java does not distinguish between null and non-existence within an API contract. Neither does Python. JS is the weird one here for having two different identifiers.
Why are you so hellbent on proving something universal that doesn't apply for the case specified above? Seriously, you're the "well, ackshually" meme in person. You are unable or unwilling to distinguish between abstract and concrete. And that makes you pretty bad engineers.
Did you read the comments above?
You can't just ignore context and proclaim some universal truth, which just happens to be your opinion.
Not for you. And certainly not for the staff working in the shop.
Currently, you're bartering with copious amounts of copium.