Hacker News new | past | comments | ask | show | jobs | submit login

I doubt most government legislators would be aware of this sort of thing (the components, libraries, and platforms that make up a given government entity's web presence).



That's the major problem. A person writing regulation to deal with this problem would need to know what a CDN is, why they are required in modern web development, the pros and cons of self-hosted vs. cloud-based analytics solutions, etc.

I really wouldn't want to be the person tasked with explaining these issues to the average politician (although some rare exceptions obviously apply).


If you step back further, this is just one example of many where regulators don't understand the consequence of their laws. You can extend this to any policy like gun control/rights, abortion, etc.

Some facts:

* We will never know the full ramifications regulation has on a market. It is impossible to calculate objectively the _full_ effect. * Regulation _always_ has unintended side effects. (Alcohol prohibition and violence, etc) * A regulator that doesn't understand the entire problem will likely increase the unintended side effects.


I totally agree with you that it is not possible for a regulator to predict the future with respect to how their decisions impact a market. However, I think that is only an argument against hasty regulation, as opposed to regulation in general.


I agree that hasty regulation would probably have more unintended side effects; however the other points still stand. Prohibition, for example, is always accompanied by a black market. There is _always_ an unintended consequence of any regulation. GDPR will likely add a tax on individuals as large companies pass through compliance expenses to us. Real privacy threats (INCLUDING THE EU) GDPR is meant to block will still continue to operate.


CDNs aren't required for delivering scripts. That's just a lazy crutch.


This is only partially true. If you import common libraries or fonts from a CDN, it is likely that the user's browser has already downloaded those previously, leading to reduced loading times because the resource is retrieved from the cache.

I'm not saying that we always have to use them, but there are cases where they can be useful.


That’s moving the goalposts. The original claim was that they’re not required.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: