5 ms·
Ah, noted. Must check and see if w3m and lynx have evolved to cope with the modern JavaScript web!
by trollied 6y ago
Ah, noted.
Must check and see if w3m and lynx have evolved to cope with the modern JavaScript web!
- Hfdlmsh 6y agow3m hasn't, thank goodness.
- reshie 6y agosome find that as a perk.
- simcop2387 6y agoElinks is the only one close, but last I tried it there were still issues
- Fnoord 6y agoTerrible suggestion. From [1] "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. [1] https://en.wikipedia.org/wiki/Elinks https://en.wikipedia.org/wiki/Elinks
- vlunkr 6y agoI don't think there's a single reason to use a text-based browser in a production environment.
- Fnoord 6y agoI think you're perfectly able to understand what I meant there: anything other than research purpose in an isolated environment e.g. sandbox.
- SomeoneFromCA 6y agobrowsing through SSH
- Koshkin 6y agoNot 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!)
- Koshkin 6y agolinks, on the other hand, is current. (Works on Windows, too.)
- anthk 6y agoedbrowse has minimal js support thru duktape.
- Tanath 6y agoBrowsh does some js, and felinks is an actively maintained fork of elinks with some js support as well.