Yep. And there's nothing wrong with that.
That they may suffer a large expense to correct years of misbehavior doesn't make me sympathetic to them.
Bummer dude. As an engineer type, I say, bring it on. Hard for me to have much sympathy ZuckerBrin can't afford another island or whatever because they made unethical decisions in the past. And if companies blow up because of it: good, that's the idea. There needs to be consequences.
Boohoo and cry me a river. Good riddance. Other companies who take care of customer data from the start will take over.
> It's government dictating the technical architecture.
No, the government doesn’t dictate technical architecture. The government dictates: be careful with personal data.
Our idea is that complying w/ data security & privacy laws should be a devops shift + costs to keep up w/ them shouldn't stop us, as developers, from keeping us just as productive in our application development lifecycle.
We're still trying to figure out the right pricing structure for smaller companies, so if you have any insight there, I'm very interested to hear it.
This harkens back to the GDPR hysteria. And that was a storm in a teacup: most companies that took compliance seriously were able to get to a good place with a medium amount of engineering work, and didn't suffer financially overmuch. A few companies did go out of business or suffer significantly--and most of those were sketchy, data-abusive entities. In other words, it worked.