2 ms·
The GDPR is far from vague, the complications come from the legalese that was used to write it. Engineers aren't lawyers and vice versa. You wouldn't want to de
by jeroenhd 5y ago
The GDPR is far from vague, the complications come from the legalese that was used to write it. Engineers aren't lawyers and vice versa. You wouldn't want to develop software thrown together by lawyers, and lawyers wouldn't want to work on law written by engineers.
It's "vague" on purpose. Had the GDPR banned cookies, companies would have switched to fingerprinting. Had the GDPR banned JS tracking, Google would've pushed Dart to Chrome. It's written that way so that companies can't think of loopholes because of the language used.
Most (European) law is written quite vaguely. The vagueness allows judges to make the right call rather than become law robots. Instead of specifying concrete limits, the law refers to the current state of the art. If you let the law decide what safeguards are or aren't appropriate, we'd be using 3DES and MD5 to this day, because that's what the law says.
We've seen what the EU does when it tries to lay down more concrete rules: they're trying to force the EU to manage certificate authorities for browsers, which is obviously a terrible idea. Crap like that is why we need vague laws.