Many browsers today are gigantic resource hogs, which are basically VMs for various web applications. On the other hand, Links is a HTML browser. It is not able to do everything. It allows me to avoid most distractions and control the content-experience. The goal of this exercise is not to force anyone to use this browser, but just to be watchful and conscious of their hypertext based internet usage (one might use gopher, and this phlog is available there, but probability tells me that a person reading this reads this from hypertext source and I am sure they are lovely).
This takes some dedication, and while I wouldn’t take it quite this far, the author does make a good point.
Noscript + adblock + some kind of firewall (piwall or similar) would be an easier solution.
I used to browse the web on Lynx (full text/no images), and then gave Links a try for a while. But was late 1990s / early 2000s. The web is no longer an upgrade of Gopher, and most web pages do not render fine in text only mode.
And, yes, this includes OSNews. Even though it is better than others (it is text heavy anyway), the menus, links, and various meta structure interweave with the actual content.
The author mentions CSS as an issue, but CSS actually solves several practical issues. For example, how can you make sure you get a sane representation on both desktop, and mobile platforms? It is possible, but not as easy, without CSS. Also there are media specific CSS that helps generate print only layouts.
I too feel nostalgic at times, but practicality wins at the end.