It’s good to see terminal-based browsers are still being developed.
I used to use w3m and lynx back in the day, and found them to be very useful at times (such as only having a GPRS signal available - makes browsing on a “full fat” browser impossible). Paired with screen (though I guess mosh would be a good option these days) to enable a resumable session in case the network dropped, of course.
Note that this isn't a "true" terminal-based browser. It's built on a WebExtension running in Firefox that renders out the DOM as text to a Go-based CLI client. It's not a browser engine running in your terminal, it's more of a VNC over TTY.
"On 17 March 2017, OpenBSD removed ELinks from its ports tree, citing concerns with security issues and lack of responsiveness from the developers.[5]"
Last stable is from 2009. Last development release 2012. Elinks is dead. Realize it uses an old version of Spidermonkey (JS). Elinks should not be used in a production environment, period.
Not just browsing (the web) - the idea of an HTML-based application UI can be extended to the text mode instead of getting stuck with the choice between a GUI and a command-line (or a custom curses-based) interface. (Imagine VSCode running in a terminal!)
I used to use w3m and lynx back in the day, and found them to be very useful at times (such as only having a GPRS signal available - makes browsing on a “full fat” browser impossible). Paired with screen (though I guess mosh would be a good option these days) to enable a resumable session in case the network dropped, of course.