4 ms·
For everyone talking about the notifications at the bottom: After the page has loaded, use “reader mode” in your browser. Most browsers have this. That shows y
by codetrotter 3y ago
For everyone talking about the notifications at the bottom:
After the page has loaded, use “reader mode” in your browser. Most browsers have this. That shows you only the text of the post, and not the notifications on the bottom.
Or, read a copy of it here:
https://web.archive.org/web/20231118211242/https://johnwhiles.com/posts/programming-as-theory https://web.archive.org/web/20231118211242/https://johnwhile...
- clysm 3y agoPeople are refusing to read out of principle. We shouldn't have to work around a bad and annoying "feature" of a site.
- newaccount74 3y agoI agree with you in general, but in this case it's worthwhile to work around the annoyance because the article makes a good point.
- josephg 3y agoToo bad. If you want to communicate that point to me, turn off epilepsy mode on your site. Perhaps my life will be worse for never knowing the point the author is making. Fine. My life is also, definitely better for not tolerating this kind of cancer.js. There are a lot of good articles out there I can read instead of this one that don’t try to punch me in the eyeballs.
- Solvency 3y agoOr don't read it, because why would I value the opinion of anyone who would implement such a feature?
- ok_dad 3y agoBecause he’s a person and people make mistakes or don’t think things through? Maybe his theory of his software was that only a few people an hour might be likely to visit his site. You should really just read the article, it’s short and good.
- deleted 3y ago[deleted]
- irrational 3y agoI left and came here to see if I was the only one that couldn’t read it because the constant movement was too distracting. I’m not going back just to do work arounds for a problem that shouldn’t exist in the first place.
- oleg_antonyan 3y agoI had to disable NoScript on that site to see what is the feature you are talking about