Slavery. For instance the technology for windmills already existed at the time, it just wasn't that big of a deal in world with an abundance of slaves. Fast forward to the Middle Ages and you find it everywhere.
Interesting, I’m starting to think undocumented thresholds are quite common in GCP.
I experienced something similar with Clod Run: inexplicable scaling events based on CPU utilization and concurrent requests (the two metrics that regulate scaling according to their docs).
After a lot of back and forth with their (premium) support it turns out there are additional criteria, smthg related to request duration, but of course nobody was able to explain in details.
Yes, we have also experienced undocumented limits for Cloud Run. For us it was an obscure quota for max network packages per second per instance. Really infuriating and took 6 months to track down what it was. I think it has been documented here now: https://cloud.google.com/run/quotas#cloud_run_bandwidth_limi...
sorry but the blame here was 100% on Mozilla. No matter which http version, headers should always be treated as case-insensitive. Blanking anything on google here is just stupid. The problem was nih-syndrome and ignored the http spec.
Mozilla are entirely clear that this was their bug.
However, GCP changing the default under their infrastructure without prior warning was still unacceptable.
Operations work should (IMO must) be conducted with the expectation that any major change like that will expose existing bugs in deployed code.
(I've done enough ops work in my life that I'd love to say 'will potentially expose' but in practice there's always -something- that breaks and if I don't find it in the first 24h after a major change I'm going to spend the next two weeks waiting for the shoe drop to happen)
GCP does send mails when you abo‘d them. GCP is not to blame if they used auto. Heck if your loadbalancer sends you headers lowercase with a new http version it should not result in a bug. GCP‘s change was fine. Their software had a bug that would‘ve led to request smuggling.
The 65k figure is what ancient historians reported, in reality it’s almost certainly order of magnitudes lower. Exaggerated figures are usually the case with ancient reports (especially about battles).
There were eight Roman legions and a lot of allied troops that had been mostly annihilated. Rome was subsequently no longer in a position to oppose Hannibal in an open field battle. From this alone one can conclude that the Roman losses must have been considerable. The figures given by Polybius and Livius may or may not be approximately correct, but I think they are in the right order of magnitude.
You can ship your local docker context to a remote host and build/run your containers there. All the docker commands you typically run locally you can run on the remote host.
thanks! I was a little bit confused at first because I've always taken docker compose as a tool mainly for spinning up dev environments. But I read mentioned article and it looks perfectly valid for single host deployments.
One thing which bothered me is how i manage container versions usually made with hashes but all you need is to either make sth like a compose template like file which would have a version placeholder or specify production compose configuration on top of the default one.
Not only they were cousins, in their private correspondence right before the outbreak of WWI they were addressing each other as Willy and Nicky[0].
By the way they fought against each other.
There's a beautiful poem in roman dialect called "the war lullaby"[0] from this period. The last two stanzas speak of this, and go something like:
Sleep tight, my darling
while this mess goes on
sleep well, as tomorrow
we'll see the kings again
exchanging pleasantries
good friends as before
they're cousins, and amongst relatives
you don't need formalities,
again will turn friendly
the personal relations.
And reunited among them
with no sign of remorse
they'll give a nice speech
on Peace and Labour
to that dumb people
spared by the gun.
I became interested in this Italian word and found this[0] casual translation: "cojone: bad word, but very useful! referring to someone who's an asshole, and stupid persons in general".
Some of the older English references[1] also seem negative: "English had it as cullion a 16c. term of contempt for a man, "a mean wretch" (Shakespeare) also "a testicle" (Chaucer), from Middle English coujon, coilon (late 14c.), from Old French coillon "testicle; worthless fellow, dolt," from Latin coleus."
I find that I can quite easily imagine the poet seeing people dying for these 'friends' while the stupid public (popolo cojone) attends a nice speech.
A "coglione", which is the Italian word for the dialectal "cojone", is literally a testicle. Anyway you can also call someone a "coglione" and it means they are somewhere between dumb, jerk and ignorant.
Agreed, macro predictions are very hard. Much easier to make predictions on individual assets (companies, commodities etc.) and hold long term.
Also, precisely because macro is hard, these analyses often feel superficial.
Inflation, especially if exogenous, can negatively impact the economy but at the same time cash-alternative assets become more attractive. What's the ultimate effect there?
And what about historically low interest rates? Don’t they warrant a shift in investment preferences towards stocks?
Wether a macro prediction turns out to be right or wrong it’s rare to read a deeper argument than “things are too high must go down”.
