That is not an understatement. This is literally the largest failing of internet infrastructure to date.
Alas, using the internet has given us a lot of efficiency. The trade off is resilience. The entire global system is more brittle than ever but it what gave it such speed.
I'd argue the infrastructure of the Internet isn't to blame here, it sounds like a software/config bug at Crowdstrike. There are wider discussions around over-reliance on cloud-based tech too. But the good old Internet can hold its head up high IMHO.
I'm not really sure cloud has much blame here either.
Imagine it's 1998 and Norton push a new definition file that makes NAV think kernel32 is a virus. The only real difference today is that always-on means we all get the update together, instead of waiting for mum to get off the phone this evening.
We got an email this morning telling us none of our usual airlines could take bookings right now. That wouldn't have been much different in 1998, airline bookings have been centralised for my entire lifetime.
In a way, this might end up being a blessing in disguise. It's an emergency drill for something potentially catastrophic (e.g. massive cyberattack, solar flare), and it's a large enough wake-up call that society can't just ignore it.
This not Internet failure but software functuality failure from a cyber security update , thios is why i never use real cloud security but rather use home cloud security on my Serverpc/NAS/SAN , when it crashes okay so be it i dont get acces to my cloud , but i allways use a online backupcloud that does not need instalation for most important stuff , u should never rely on 1 softweare to do all allways have backups
Indeed this is different , This is world wide and it does not even only affect Windows pcs but with some friends of mine Linux and Macs are in trouble 2 , this is not ur Windows Vista BS problem etc
It’s most likely the flame war filtering algorithm of HN. Posts that create a lot of discussion quickly are down ranked until an admin fix the rank manually, or not.
For other JS developers the stuff about await isn't relevant. It's not the same as a JS async/await
In JS an await is just syntactic sugar around a then() on a promise. The Await in the article is a method to block the thread until a promise resolves, there is no equivalent in JS.
.NET has a similar mechanism with Task.Result with similar pitfalls