Futurelock is not about cancellation safety (cancellation is actually one solution to futurelock), though the related issues that are linked in that post are.
At an early stage startup, shipping a feature should not require "many meetings across product, legal, and engineering". Especially not one that can be mostly built in a day.
I am very happy that I can charge my phone and laptop from the same charger, and don't ever have to worry about whether the cable I'm using will be a fire hazard.
I think the real issue here is that two Android phones take photos with incompatible naming schemes.
I am sure that at some point someone thought the milliseconds should or should not be separated from the seconds and made that change without thinking through the consequences.
I don't think that's true. I have seen R4L folks reiterate time and again that C changes are allowed to break Rust code, and they will be the ones to fix it.
Big tech can be suprisingly not locked down!