>It goes over my head why Cloudflare is HN's darling while others like Google, Microsoft and AWS don't usually enjoy the same treatment.
Do the others you mentioned provide such detailed outage reports, within 24 hours of an incident? I’ve never seen others share the actual code that related to the incident.
Or the CEO or CTO replying to comments here?
>Press Release
This is not press release, they always did these outage posts from the start of the company.
> Do the others you mentioned provide such detailed outage reports, within 24 hours of an incident? I’ve never seen others share the actual code that related to the incident.
The code sample might as well be COBOL for people not familiar with Rust and its error handling semantics.
> Or the CEO or CTO replying to comments here?
I've looked around the thread and I haven't seen the CTO here nor the CEO, probably I'm not familiar with their usernames and that's on me.
> This is not press release, they always did these outage posts from the start of the company.
My mistake calling them press releases. Newspapers and online publications also skim this outage report to inform their news stories.
I wasn't clear enough on my previous comment. I'd like all major players in the internet and web infrastructure to be held to higher standards. As it stands when it comes to them or the tech department of a retail store the retail store must answer to more laws when surface area of combined activities is took into account.
Yes, Cloudflare excels where others don't or barely bother and I too enjoyed the pretty graphs, diagrams and I've learned some nifty Rust tricks.
EDIT: I've removed some unwarranted snark from my comment which I apologize for.
Yes. The problem wasn’t the airframe, nor even frankly the engines, it was the combination plus the decision to fix an aerodynamic instability with an undocumented software patch.
That last part is key: the MCAS system was designed to fake handling like the older planes but they skimped on safety to save the cost of a second sensor and didn’t train pilots on it or have an override mechanism. If the whole thing had been aboveboard they’d have saved so many lives…
There was an override system, MCAS drove the stabiliser trim motors and so flipping the stabiliser trim motor cutout switches would disable MCAS. This relied on the pilots diagnosing an MCAS runaway as a stabiliser trim runaway and enacting the same checklist.
However, to add insult to injury, the MAX also had another change. In the 737 NG, there were two switches, one would disable automated movement of stabiliser trim, the other would cutout the electric trim motors entirely. This allowed the pilots to disable automation without losing the ability to trim the aircraft using the switches on the yoke.
The MAX changed this arrangement, now either switch would cut power to electric trim. Tragically the pilots of Ethiopian Airlines Flight 302 recognised the runaway, enacted the correct checklist, but the aircraft was now so far out of trim that aerodynamic loads made correcting the situation using the hand trim crank impossible. In desperation the pilots restored electrical power to the trim motors, MCAS re-engaged and drove the aircraft into the ground.
reply