5 ms·
The points brought up by @cromwellian in https://news.ycombinator.com/item?id=24416738 https://news.ycombinator.com/item?id=24416738 are important in the contex
by tomayac 6y ago
The points brought up by @cromwellian in https://news.ycombinator.com/item?id=24416738 https://news.ycombinator.com/item?id=24416738 are important in the context of the present comment, too.
- nuker 6y agocromwellian > "But what really bothers me is people making uninformed comments. Rather than knee jerk trigger anytime any browser API is changed without fully reading the spec and then actually pointing out any weaknesses, we get the same low signal commentaries." This may sound dumb too, but I expect my browser just show me web. When I reset my browser (and IP address), I expect a clean slate, and with this API I won't get it. When I install apps, I use very different due diligence. Without clean slate after resetting my browser, I'd have to change my browsing habits radically [0]. A side note, DNS over HTTP (DoH) bothers me too, spec is silent about setting cookies, DoT is cleaner in this regard. [0] https://en.wikipedia.org/wiki/Chilling_effect https://en.wikipedia.org/wiki/Chilling_effect
- rewq4321 6y ago> When I reset my browser (and IP address), I expect a clean slate, and with this API I won't get it. Browsers don't currently give you that, and never have. You can download files, and these files remain on your system even if you re-install your browser. > This may sound dumb too, but I expect my browser just show me web. Browsers are just a sandbox for running applications that are downloaded over the network. Some applications need web cam access, some need access to files on your system, some need geolocation, and so on. Browsers let you choose what permissions to give applications. Because of this, you're completely free to let your browser just "show you the web" in whatever sense you like.