I mean, the last fappening was done by phishing, as I recall. Are you saying another one, done by rowhammer, wouldn't be a problem?
I suspect most folks have stuff they'd rather not make public. Credit card numbers, at the very least. This affects us all.
Similarly the day-to-day ransomwares probably cost more than securing browsers will.
If it comes you'll hear about "apps" that freeze every other browser process while you do online banking.
That said, proactively blocking JS is great for many reasons, and you can whitelist sites you sort of trust.
This is a pretty laissez-faire attitude with regards to security-critical exploits. You might be the one of the first ones affected. After all, someone has to be first one before they can post it on HN.
In a more general sense, it's a bad idea to rely on someone else as your primary alert. Whether it is a HN post, news article, whatever.
(I know that you aren't quite saying to use it as a primary alert, but a cursory read of your comment implies it, so it's worth discussing.)
If you are regularly the fist target of zero-days your threat model should be stricter yes. The other 7.9 billion people in the world can afford to be a little less strict.
It did come to that, years ago: https://github.com/IAIK/rowhammerjs
Something about CPU firmware and its inability to fix some aspect of memory bank controllers.
I've been browsing with Javascript off-by-default for years and recommend it regardless.
Sure, perhaps a site I trusted and whitelisted will try to hack me, but I feel it's far less likely than some random typo-squatting site or advertising-broker logic.
Not at all. It is another one of the Chicken Little's security theater that sound sexy and sophisticated but in practice mean nothing.
If you are concerned about this issue you should first ensure that you never type "npm install" or copy something off Stack Overflow into your code.
https://github.com/IAIK/rowhammerjs
This has existed for years and its use has been observed in the wild. RowHammer isn't new.
You pulling 15Gb of Nodejs modules in your app that you have no idea about because you think someone, somewhere ensured that they are "correct" importing a supply chain attacks works every single time.