Kind of normal I think, at the companies I've worked for, most outages were caused by a change in production, for which the impact was not properly assessed.
This could actually be extremely convenient to use in many parts of Africa where place simply do not have addresses. Right now what we do is latitude longitude, which works wonders but can a bit clunky especially in cities
I haven't read that book, but asked for a summary.
Honestly, I cannot see software being regulated the same way as food industry is, for the very simple reason that software can trivially cross borders (legally or not) while food cannot. Regulating that industry to prevent any progress by erecting bureaucratic barriers in a given country will just kill the industry in that country and make it thrive elsewhere where it's less regulated. As a result, the regulation-freak country will lose any of its competitive advantages due to lesser efficiency.
Doing this on a global scale requires "CFC-ban"-levels of global coordination which I cannot see happening in the world we live in today. Just look at how global CO2 reduction and climate change is being handled today at the global scale.
Really? It is up to them if they want to use what I wrote. Why would I get fined or jailed for not writing documentation? Good luck trying to prove any wrongdoing. If you want support feel free to hire me to do that, or just do it yourself, pretty much like big tech is doing right now with open source
A serious security issue indeed, if someone knows the hash.
How I manage this is that every time I want to open-source a previously private feature, I take the changeset diff and apply that to the files in the public repository. Same features, but plausibly different hash.
Transitioning from CentOS 7 to RedHat 8 and 9 at my former company's private cloud has smooth for most teams, pareto-style, with 80% of migration-related incidents caused by the 20% of the teams that did some really weird changes to the VM's OS that was no longer allowed under RHEL 8 or 9.
At first, I thought it was just to reduce the complexity of managing hardening rules for several OS and OS versions.
In general I think punishing mostly innocent individuals for a decision made by their government is a terrible way to proceed. Furthermore with the 1-week notice you're literally urging people to get off your own platform. I don't condone the Russian-Ukraine war, but just because you take a political stand -- legitimate or not -- doesn't mean it's fair to put undue pressure on .ru domain owners just because those TLDs happen to be Russian (are they even reimbursed?).
I'm not picking any sides here but I won't use Namecheap if I know it can deny me service on a whim just because the government of the country I have registered my domain name in has gone to war with another country. War is force majeure but Namecheap really didn't have to do this: it makes them an unreliable provider in regard to the current world's political instability.
Well there are so many rules and official norms (approx. 400,000) and exceptions about pretty much anything in France that this is pretty accurate... Just look up the rules of the road regarding phone calls while driving for examples and see how it has evolved over time: specifically holding the phone was forbidden but using headphones were explicitly allowed until the latter also got banned by another law a few years back. Now to have calls we must put our phones on speakers (but not too loud) and use both hands for driving, effectively forbidding us to give any calls while driving all that without explicitly saying so.
It's hardly enforceable, but wait until you encounter a zealous police agent that's been tasked to give a certain amount of tickets