Not a CS fanboy, but just wanted to suggest an alternative to sheer incompetence
Not a CS fanboy, but just wanted to suggest an alternative to sheer incompetence
They know that mistakes can take out thousands and thousands of devices, therefore it is imperative they prioritize stability over rollout speed. They have more direct access to devices, than any 0-day would ever have, therefore there is a significant risk that they do more damage with an update than any 0-day ever could.
You have to remember, a 0-day could come to existence that threatens every system, but that usually happens once every couple of years (last one of that category was probably Blaster/I LOVE YOU). But CS risks of damaging the system every couple of hours with an update. Therefore, it should be tested to make absolutely sure it doesn't cause crashes.
IMHO, it was sheer negligence and incompetence.
1. They run inside a kernel.
2. They have many clients. (Incl. hospitals?)
This implies serious severity and impact of potential incidents, so in turn it should imply certain level of quality assurance process.
As we witnessed, it has glaring holes.