News for hackers. Stuff that matters.
Re:Deconstructing Google’s excuses on tracking protection by jakeogh on Friday August 23, 2019 @02:31PM (#20780893)
And disable JS. The idea that clients need to execute arb code to see a page broke the information / presentation separation, on purpose. I leave it off (surf lets you easily toggle it per process), and it's pretty rare that I actually want to use it, and in those cases, the page could easily have been designed to work fine without it. It's a deliberate problem.
Re:Deconstructing Google’s excuses on tracking protection by joes223 on Saturday August 24, 2019 @02:38AM (#20785644)
Afaik, TeX is a Turing-complete language that can even read files from disk. Yet, it's only purpose is to render static text documents and nobody blames Knuth for inability to separate the presentation layer. The web is no longer a bunch of text documents. It's the first and only successful cross-platform solution. Moreover, it's still in the very infancy and in 10-20 years it will be the full-blown operation system layer on top of every platform. The problem of the web is that its sandbox has become leaky.
Re:Deconstructing Google’s excuses on tracking protection by jakeogh on Sunday August 25, 2019 @01:19AM (#20791500)
Me: executing arb code to view a doc is a bad idea

You: TeX is turing complete too!

Great. Thanks.

Re:Deconstructing Google’s excuses on tracking protection by la_barba on Friday August 23, 2019 @06:24PM (#20783292)
Not to mention all the CPU time that JS scripts eat up. The eco-impact of disabling JS world-wide will be significant...