10 ms·
I feel like many of the text-mode browsers have failed to keep up with changing web standards. We were all mad when IE was holding back the Internet, and I'm n
by jrockway 7y ago
I feel like many of the text-mode browsers have failed to keep up with changing web standards. We were all mad when IE was holding back the Internet, and I'm not sure we should give lynx and w3m a pass because they're geek tools. (Accessibility is an important concern, but web browsers running under a GUI system support screen readers.)
https://www.brow.sh/ https://www.brow.sh/ is a console-based browser that claims to support modern standards. Perhaps that is what we should be using.
(I am now prepared for 6 comments replying to me saying that anything that can be implemented with HTML from 1999 should be, and a list of search results can be. I guess. If all that stuff works for everyone, why did we invent new stuff? Just because? Or perhaps it wasn't really as amazing as well all remember.)
- 1996 7y agow3m gets a pass because javascript is bad. The FSF is right about that. wasm will be even worse. Not technically worse, but for removing another layer of control. DNS over HTTPS is just as bad in that sense. If you can make something without JS you should. cryptomarketplot.com has an accessible mode FOR CRYPTO!! If crypto sites can, everybody can.
- asveikau 7y agoIt's funny because "javascript is bad" was common geek sentiment at the turn of the century. Now it is flamebait, or being caught up in the past [itself possibly a bit of a code for ageism]. Seeing this attitude change is one of the most interesting things I've seen in tech nerd circles in the last decade or so.
- juststeve 7y agoCan you elaborate on why it's funny? javascript (on it's own) has changed a lot in 20 years and it was originally designed in what, one week due to external time constraints? i think the criticisms are valid if $Your_favorite_language had ~4 days only for language design. From my recollection, there were no frameworks, no tooling, no linters, no jquery. it was a basically a primative language for browsers that had no compiler and didn't do anything useful (back in the 90's). About as exciting as VBA 1.0.
- asveikau 7y agoIt's funny to see attitudes change so dramatically is all I mean. I think you may be blind to the harshest criticisms, though. It was a common view that the web was built for static content (or server-side dynamic content) and code execution by the client is mostly a nuisance at best. And there is some validity to that. When JS was developed, roughly contemporaneous with worse ideas like java applets and ActiveX on the web, it was thought by proponents that untrusted code execution is OK to good. 20 years later, it was still assumed that if JS is sandboxed, memory safe, has a different page table from the rest of user mode, untrusted code execution is safe. Then spectre and meltdown happened.
- juststeve 7y agoYeah there's some hindsight there... but are you saying that views have gone full circle? Where are these attitudes changing? JS has historically been sandboxed better than Java Applets and ActiveX, which is one reason why it's popular now.
- asveikau 7y agoNope, not saying they went full circle, just that they went from one extreme (client side code bad) to another (client side code as inevitable fact of life and why question that?). And tangentially, I was pointing out more recently that the grumpy position from older times actually would have prevented some real world problems. (Spectre and meltdown go from being local privilege escalation bugs to "holy shit you can own my machine if I visit a web page")
- neop1x 7y agoJavaScript was made to add a bit of interactivity to webpages. Like "click the button to expand the text". What is it now? There are whole javascript frameworks being made. Maybe soon web(sites) won't even use HTML anymore but rather render custom UI to a canvas. Browsers are new operating systems running on top OS. Lots of performance wasted by this. Yes, there are webapps using it wisely, although JS is often misused on sites which could have been plain html or html+ajax. In many cases CPU is not even doing much but some webs take 2 seconds or more until I start seing some graphical output after entering URL. It takes a lot of time to render templates and construct DOM. Pretty sad.
- jlg23 7y agoOne does not need to time travel to 1999 to accommodate text browsers, current HTML works just fine. OTOH I don't worry too much, accessibility-enforcing laws will provide plenty of job opportunities for future developers... So yeah, good move, I guess.
- TeMPOraL 7y agoI'll be the first (EDIT: third) of six. > If all that stuff works for everyone, why did we invent new stuff? Just because? Or perhaps it wasn't really as amazing as well all remember. To better track people and push ads. It's really mostly just it. Modern web has very little to do with providing value to the end-user; any utility that's provided is mostly a side effect, and/or a vector to lure people into situations where they can be monetized. Text browsers aren't holding the web down, they're anchoring it in the port of productivity, even as the winds of commerce desperately try to blow it onto the open seas of exploitation.
- javajosh 7y ago>Modern web has very little to do with providing value to the end-user I disagree strongly with this. The web has moved a lot in the direction of developer experience (ES6, modules) and new capabilities (WebSockets, WebRTC, WebAudio, SVG, canvas...). Yes, most of this happened because it's a side-effect of big surveillance capitalism companies wanting make that sweet sweet digital pollen to be even sweeter, but that doesn't make it any less sweet just because it was made in bad faith.
- TeMPOraL 7y agoThe capabilities are there. The dev experience is there (somewhat; JS ecosystem is a mess, but I guess that's just a side effect of moving very fast). But the capabilities are not used for end-user benefit. Not much, anyway. Yes, I benefit from Netflix, I benefit from Google products (not as much as I would if they didn't keep on worsening the UX every few months) - and such functionality requires some of the new capabilities. But 99% of other sites I visit don't use these capabilities for anything good. A pizza ordering site shouldn't need a React frontend. An e-commerce store shouldn't use WebSockets. Every other site out there should not ask me to enable notifications. But they all do. I blame a mix of CV-driven development, designers showing off, "data-driven" bandwagon, and surveillance capitalism.
- javajosh 7y agoI agree with you on all points - I think we're just speaking past each other. I'm speaking about the platform, and you're speaking about applications. The applications written for the web today are exactly as you say; the browser platform itself, however, is quite extraordinary and I remain deeply impressed with it.
- deleted 7y ago[deleted]
- superkuh 7y ago> brow.sh Does headless Firefox (what brow.sh is at it's core) even launch if there's no X11 available? Is it that headless?
- caleb-allen 7y agoI've played with it and it works over a headless server instance through an ssh session, so I think it does not require X11
- Arnavion 7y agoI haven't used it, but it works in a Docker container without any device mounting or access to the host X server, so I'd assume that it does indeed work without any X available.
- deleted 7y ago[deleted]
- Piskvorrr 7y agoIt does work without an external X11 all right (trick question, actually, there's an Xvfb underneath all the turtles - so X11 actually is required, even though it's all hidden inside the container ;))
- quickthrower2 7y ago> I am now prepared for 6 comments replying to me saying that anything that can be implemented with HTML from 1999 should be, and a list of search results can be. They would be correct replies! In addition there is this concept called "graceful degradation", where if the browser has more advanced features, you support them, otherwise you work anyway. It's not like supporting Lynx means you can't have a map in the search results when using Chrome. Certainly not for a company with the resources of Google. Also they should probably send something like a Lynx-version of Google down to people with a poor internet connection.
- birdyrooster 7y agoThey probably are hiring only the best machine learning, cloud-native engineers fresh out of university who have never heard of lynx and now the institution doesn’t even realize it broke support for it.
- jordigh 7y ago> I feel like many of the text-mode browsers have failed to keep up with changing web standards Yeah, web standards such as images and video and audio. Not keeping up with those standards is kind of the point.
- miracle2k 7y agoThanks for making me aware of brow.sh. What an amazing project.
- mumblemumble 7y ago> We were all mad when IE was holding back the Internet As I recall it, we weren't mad about IE "holding back the Internet", we were mad about IE encouraging web designers to stick a bunch of dynamic clutter such as ActiveX controls into their webpages. Largely because they created this lock-in where sites only worked well on one browser. It turns out that JavaScript has been co-opted into being the new ActiveX, and Chrome is the new IE. But since JavaScript is nominally an open standard, and Chrome runs on the big 3 OSes, nobody seems to get mad that alternative browser projects are dying because they can't keep up with all the stuff that needs to be implemented in order to work well with sites that were only tested on Chrome and WebKit.
- Piskvorrr 7y agoAmen, amen! The ignominous "best viewed in" which we fought in the Second Browser War is creeping back in - except now it says "this hour's current Google Chrome" instead of "MSIE 6".
- mumblemumble 7y agoTBH, I think it's worse than it was with IE6. Targeting just IE was annoying, but, even so, 20 years ago, I could use BeOS as my primary desktop OS, and Net+ was a decent enough browser. Nowadays, the bar to successfully render a modern JavaScript-heavy website is so high that even Microsoft couldn't successfully maintain their own independent rendering engine, and is shifting over to Google's. Anyone who has heard of the phrase "embrace, extend, extinguish" should be at least a little bit uncomfortable with this situation. For example, it implies that any potential alternative OS needs to be able to compile Chromium (or, as what can only be seen as a second-class substitute nowadays, Gecko) before it can really be viable. If you're the kind of person who likes a free, open and competitive software landscape, that's a looming threat.
- Piskvorrr 7y agoThat's a different issue altogether, but still salient. - 1. you need a beefy device to render in a reasonable timeframe and - 2. you need The One Blessed Renderer to even see anything I do recall the situation 20 years ago, when I could use about 2/3 of the relevant Net, with the rest going "meh, chronic complainer, just use IE. What? Yeah, that's your own fault for not choosing Windows." The second part is far more worrying, as it is not resolvable locally, either by optimization, or by horsepower.
- wwweston 7y ago> I am now prepared for 6 comments Not sure that's the case, if so, I'd expect a comment that shows a little deeper understanding of the issues involved. "HTML from 1999" isn't the issue. Lynx did fine on that... and HTML from 5 years ago, just like a whole host of non-visual or semi-visual user agents. brow.sh is... OK, I guess, nice to have around in a pinch, but like most other schemes that rely on a headless full-fledged browser in order to work with applications that have become dependent on JS to merely render content it introduces a glorified screen-scraping layer to something that can easily be much simpler, assuming web application developers can be bothered to think about it. We don't need to freeze the web at 1999, and some applications fit poorly in a non-visual context. But a little bit of reflection on how the merits of progressive enhancement and moving forward without losing the benefits we had at that stage would be nice. The stage where people cared about such things was pretty amazing in terms of the breadth of devices web applications would in fact work on pretty well. Also, if you're not thinking about pretty plain HTML version of your app, chances are half decent you're missing an opportunity to engineer your application better whether or not you care about UA interop. But, you know, if you're pretty sure the browser should be "thought" about as nothing more than The VM That Lived™, by all means, carry on.
- iteratorloopmap 7y agoI use text browsers because they are efficient and fast. Also Static content shouldn't ideally need js because it is a security concern. AFAIK most of us don't complain when a dynamic website doesn't work. We just use a modern browser.