I don't think a stable ABI has enough advantages to be worth it. C++, IMHO, is a great examples of the downsides of a stable-enough ABI, where stability was never guaranteed, but is now so entrenched that it'll likely never be broken again (limiting the language & the usability in a bunch of ways).
It might make sense to have a subset Swift-style stable ABI, but that's a huge engineering effort, has lots of overhead and is also likely not worth it IMHO.
> The FAA has one of my favorite examples of thoughtful rulemaking. They haven't banned flying with a baby on your lap, because the extra cost would mean many parents would drive instead. Since driving is far less safe than flying, a ban would lead to more deaths. I'd love to see more of this "all things considered" thinking around bans.
In terms of CO2e, a familiy of 2 + a kid driving a car instead of flying results in quite a bit of less emissions. Depending on the assumed mortality per tonne CO2e, driving might lead to a lot less deaths.
This is of course quite unreliable data, but one example of just to say how "all things considered" is very hard and almost always still comes down to a judgement call.
Yes. This. We all - and especially parents - spend all day every day evaluating risks. The FAA does not need to decide for me the level of risk between holding a baby in my arms vs having it in a sling during take off and landing. That's very silly.
For real. For something like car seats, arguably the regulation was what we needed to get them adopted. This though, seems as necessary as government regulators deciding if I can babywear my child when walking down the street. The relative risks and benefits are impossible to fully compare with this issue, and the impact on other people is nil whether it's baby in lap or baby in carrier.
> WhatsApp is similar by the way. Unless you enable E2E backups, they end up in iCloud/Google Drive backups and are only encrypted at rest
One of the few good things about WhatsApp is that Meta can very credibly claim that they can't access the backups (as they're not stored by Meta). Meta holds the encryption key & Google/Apple hold the backups, so at least you now have deal with two entities to get the data.
I don't think without forcing more customers to loose data (e.g. by requiring them keeping an encryption pin/key) it's possible to perform backups in a (much) better way.
> I don't think without forcing more customers to loose data (e.g. by requiring them keeping an encryption pin/key) it's possible to perform backups in a (much) better way.
I have full confidence that the industry would be quick to innovate if they were forced to, but that's not in their interest nor the government's interest.
Here's a simple one: Build an open standards-based system where users choose their backup provider and let them decide whether they prefer to have full control over the encryption keys or whether they want them to be managed by a third party. Educate them so that they can at least try to make an informed decision. Warn them about the risks and jurisdictions of built-in providers.
If someone wants to continue using their device as-is? Cool, 2 taps and they're done.
Do they want to store all of their app backups on their NAS? Make it as easy as switching your default browser.
> Here's a simple one: Build an open standards-based system where users choose their backup provider and let them decide whether they prefer to have full control over the encryption keys or whether they want them to be managed by a third party. Educate them so that they can at least try to make an informed decision. Warn them about the risks and jurisdictions of built-in providers.
WhatsApp performs (on Android) backups inside a normal directory. You can just backup it via e.g. Syncthing, which I've done in the past.
It doesn't get much more standards based. Strongly pushing users to deviate from the standard flow IMHO risks them quickly choosing poorer options (e.g. a free, dubious, online hoster). At least with the current setup, the "easy option" is quite safe in terms of not loosing data and very low risk that anyone apart from you and governments with lawful access ever accesses the data.
I see, I wasn't familiar with the way WhatsApp does this. I was talking more broadly about iOS/Android app data backups in general.
> At least with the current setup, the "easy option" is quite safe in terms of not loosing data and very low risk that anyone apart from you and governments with lawful access ever accesses the data.
The backups would still be encrypted and you could even have Apple/Google hold onto the key (if you wanted to), but if the data was stored elsewhere then neither party could access it unilaterally.
I'd argue that should/could be relevant, but isn't in reality. Do two global data processors more happy to work with governments/law enforcement exist?
It might make sense to have a subset Swift-style stable ABI, but that's a huge engineering effort, has lots of overhead and is also likely not worth it IMHO.
reply