Reading privileged memory with a side-channel

Re:Reading privileged memory with a side-channel by nostrademons on Wednesday January 03, 2018 @09:04PM (#16067402)

As a developer, it's even easier to test without Javascript: open Chrome Developer Tools, select Settings from the hamburger menu, and check "Disable Javascript".

As the other comments point out, though, the biggest problem is that this is economically irrational for most site owners. The figures on JS-disabled usage I had when I was still at Google (3+ years ago now) were at the lower end of TikiTDO's range. It generally doesn't make economic sense to spend developer time on an experience used by 0.1% of users, particularly if this requires compromises for the 99.9% of users who do have JS enabled.

[ Parent | on HN ]

Re:Reading privileged memory with a side-channel by confounded on Thursday January 04, 2018 @02:28AM (#16068629)

Culling all that JS can make things faster for everyone.

If you have a web app there’s no point, but if you’re displaying text and images and your site doesn’t work without JS, you’ve over-egged a solved problem.

(... While increasing perceived latency, especially for mobile users.)

[ Parent | on HN ]

Re:Reading privileged memory with a side-channel by keltor on Wednesday January 03, 2018 @10:58PM (#16067935)

I'd bet a certain percentage of THOSE were actually lynx/links/elinks users rather than no script users.

[ Parent | on HN ]