The problem with standardization of anything in law is that inevitably it slows down innovation a bit. That's obviously not a problem with something like housing, but in tech it might be an issue.
I'd rather have "ideological" bills that explicitly say companies can't take the piss, empowering judges to throw the book at them with liberal interpretations.
This isn't about tech though. It's about Terms of Service. The Legal Contract between the tech company and the user. I don't see where "innovation" comes into this other than disadvantaging the user.
Anybody who followed the evolution of GPL knows changes in technology absolutely affected the legal setup around such technology (and viceversa). Neither side operates into a vacuum.
Note I'm not completely contrary to a legal intervention in the matter (the EULA concept must die); just that it makes more sense to put in law that companies must not take the piss, not that they can take the piss as long as they follow the letter of some standard form. Then they can absolutely follow with standard guidelines that are somewhat advisory, as a way to speed up enforcement; but it's important that the law establishes overall principles, so that it's more future-proof.
Do I need innovation in a subscription agreements? I dont think so. If I am paying X for service I dont need any innovative interpretation of what it means. I just want my service delivered..
> The problem with standardization of anything in law is that inevitably it slows down innovation a bit. That's obviously not a problem with something like housing, but in tech it might be an issue.
Software development is the side where I'd expect the most slow-down (rather than EULAs) but if anything, I think standardisation removes friction from innovation — I'm much more likely to adopt your lib for example if you tell me it's MIT licensed rather than something you've written something a bespoke library for.
Similarly, imagine if a new start-up creates a new Alexa competitor, say — I'd much prefer if they said "we treat your personal data as standard, under this commons licence. Then, we also have some niche requirements that are A/B/C and this is how they explicitly work", rather than pages long TOS that I need to go through with a fine-tooth comb to see if anything has been snuck in.
The problem with standardization of anything in law is that inevitably it slows down innovation a bit. That's obviously not a problem with something like housing, but in tech it might be an issue.
I'd rather have "ideological" bills that explicitly say companies can't take the piss, empowering judges to throw the book at them with liberal interpretations.
This isn't about tech though. It's about Terms of Service. The Legal Contract between the tech company and the user. I don't see where "innovation" comes into this other than disadvantaging the user.
Anybody who followed the evolution of GPL knows changes in technology absolutely affected the legal setup around such technology (and viceversa). Neither side operates into a vacuum.
Note I'm not completely contrary to a legal intervention in the matter (the EULA concept must die); just that it makes more sense to put in law that companies must not take the piss, not that they can take the piss as long as they follow the letter of some standard form. Then they can absolutely follow with standard guidelines that are somewhat advisory, as a way to speed up enforcement; but it's important that the law establishes overall principles, so that it's more future-proof.
1 reply →
Do I need innovation in a subscription agreements? I dont think so. If I am paying X for service I dont need any innovative interpretation of what it means. I just want my service delivered..
> The problem with standardization of anything in law is that inevitably it slows down innovation a bit. That's obviously not a problem with something like housing, but in tech it might be an issue.
Software development is the side where I'd expect the most slow-down (rather than EULAs) but if anything, I think standardisation removes friction from innovation — I'm much more likely to adopt your lib for example if you tell me it's MIT licensed rather than something you've written something a bespoke library for.
Similarly, imagine if a new start-up creates a new Alexa competitor, say — I'd much prefer if they said "we treat your personal data as standard, under this commons licence. Then, we also have some niche requirements that are A/B/C and this is how they explicitly work", rather than pages long TOS that I need to go through with a fine-tooth comb to see if anything has been snuck in.