4 ms·
HTML should never have grown into the mutated application runtime it is today. The presentational concerns for documents are different from application renderin
by echelon 7y ago
HTML should never have grown into the mutated application runtime it is today. The presentational concerns for documents are different from application rendering. The javascript stack should have been something entirely separate.
I strongly feel we should create a lightweight HTML fork that is again document-centric and doesn't allow for all of this javascript nonsense. Something that doesn't allow for stupid custom UI or behavioural tracking. Just text, images, videos, and links. The painting algorithm would be dead simple, documents would load lightning fast, and we'd be confident there would be no ad malware.
- frank2 7y agoCreating it is the easy part, IMO. The hard part is to get people to publish on it. I fear that most authors (and most creators of images and links) are not knowledgeable enough to see the web's shortcomings and that it will be very hard to explain the shortcoming to them -- with the result that most authors will continue to consider their job to be done once they have put their writings (and images and links) on the web.
- compressedgas 7y agoIt already exists and it is called HTML. It is how JS is used to load page contents that can not be tolerated. Follow progressive enhancement. No JS should be required to load the contents of a page. If JS is included it should be to replace what would otherwise require a full page reload. If it is not possible to load the contents of a page without JS or the JS fails to complete, then the page should show its alternative contents. The page shall under no case be left blank. This is graceful degradation.
- frank2 7y ago>Follow progressive enhancement. . . . This is advice for a web site owner, and I don't see giving advice to web site owners to be an effective way to help internet users who are very annoyed with the web like I am. Web site owners are embedded in an ecosystem controlled by entities such as Google and Mozilla who either don't know or don't care about the dissatisfaction I and people like me have with the web. I have come to believe that the best way to help internet users who are sufficiently like me is not to try to improve or change the web, but rather to start a new internet service outside of the control of Google, Mozilla, etc. Great grandparent seems to have come to a similar conclusion. Modern web browsers are designed to satisfy goals X, Y Z, U and W. You are pointing out that browsers can be used to do X. I (along with great grandparent IIUC) are replying, yes, it can, but a new service designed to do X alone will probably do it better with fewer bugs and glitches. And all the web site owners with goals Y, Z, U and W are really getting in our way when we pursue X; our moving to the new service would give us a way to separate ourselves a little from those site owners, saving us a lot of time and annoyance.
- userbinator 7y agoI strongly feel we should create a lightweight HTML fork that is again document-centric and doesn't allow for all of this javascript nonsense. Something that doesn't allow for stupid custom UI or behavioural tracking. Just text, images, videos, and links. HTML already has such a mode. It's called "turn off JavaScript". Fortunately, there are still plenty of good sites in that style. (You can still have ads with plain HTML; they just aren't as annoying nor intrusive.)
- VRay 7y agoWhere do you get your news and stuff without JavaScript? I think HackerNews is just about the only website I regularly use nowadays that works without JavaScript
- userbinator 7y agoI can read the news on https://www.bbc.co.uk/ https://www.bbc.co.uk/ without JS, for example.
- kristopolous 7y agoBrowse tor. It's like the 90s web with better server side scripts. No ads, no JavaScript, small page footprints. It's fantastic. The practice of website building on it is a great model for how to fix the web.
- indymike 7y agoI'm not so sure that the evolution of HTML could or should have been different. The second thing I ever did with images and text was link them to other pages and arrange them in the form of a menu. When I learned to use CGI, the first or second thing I did was write a script to generate pretty menus. The web's UI is a document-as-app model... documents that use a small set of interactive elements to create a cohesive and useful experience. It beat many competitors that were applications for displaying documents. Document as app works really well. Users understand it. It costs less to develop than old UI guidelines defined desktop apps. And is portable to users on diverse systems... Web apps (and web pages) have succeeded where entire generations of cross-platform tech has failed... or succeeded mildly.
- jim-jim-jim 7y agoSounds like you're describing Gopher.
- untog 7y agoWe already know what happens when that system is created, though. Because it’s what the web used to be. And the result was that people hacked around it: rendering entire page structures as static, unresponsive images. And that’s exactly what would happen again.
- newsbinator 7y agoTo be fair, at the time we were trying to implement the print world on computer screens. People (i.e. stakeholders) weren't used to responsive text and images yet. They wanted to tell the pixels on a web page precisely what to show.
- roca 7y agoThis idea comes up often. I think it's a bad idea for many reasons, so rather than repeat myself I wrote them down here: https://robert.ocallahan.org/2020/05/why-forking-html-into-static-language.html https://robert.ocallahan.org/2020/05/why-forking-html-into-s...
- compressedgas 7y agoWhat you want is for web authors to follow progressive enhancement. No JS should be required to load the contents of the page. If JS is included it should be to replace what would otherwise require a full page reload.