4 ms·

HTML is just a datastructure, we just happen to use it more heavily than most. I think she makes a lot of very valid points, Web 3.0 is abandoning its foundati

• saagarjha 9y ago
  > HTML is just a datastructure Sure, that's a nice way to put it. If you remove data from it using its normal contract, of course it's bound to behavior reasonably well. If you go and take a linked list and start zeroing out random bits of a node's next pointer, of course it isn't going to work, and the same is true with HTML.
  • tomc1985 9y ago
    A good linked list implementation will also allow you to delete nodes through its normal contract
    • saagarjha 9y ago
      Yes, that's what I'm getting at. If you delete a linked list's nodes through the normal way of doing it, nothing goes wrong. If you do bad things to it bad things will happen.
  • stephengillie 9y ago
    If you delete a div from the DOM, nested divs are deleted as well. This is the core to a new site engine I've built[0]. It takes a JSON representation of a single-page application, and dynamically constructs pages within the browser. The resulting page is very fast and lightweight, especially on mobile, as there are almost no server calls involved. The Node engine is less than 200 LOC and the client is less than 600 - both are smaller than the JSON file for the main site. I'm building a hosting service for this new type of site, hoping to launch before end of summer[1]. [0] https://gilpublic.s3.amazonaws.com/Gilgamech.js https://gilpublic.s3.amazonaws.com/Gilgamech.js [1] https://www.SPArational.com https://www.SPArational.com
    • jakobegger 9y ago
      Did you read that part about the upside down pyramid? I‘m not sure this article is the best place to pitch your project...
      • deleted 9y ago
        [deleted]
      • stephengillie 9y ago
        Part of the goal of this project is to abstract the data of a site's construction further from its presentation. Sites, and parts of sites, are very portable and transparent. You can move a div around a page simply by changing the parent element specified in the 'elementParent' field of the HTML element you're describing. And you can copy divs, pages, even whole sites, more easily than server-hosted HTML sites. Being in a more formal data structure lends sites to more automation, working with data objects alongside string parsing. The browser engine is meant to be as minimal as possible, and could be easily replaced by a native browser function that ingests JSON to display pages. CSS still works normally, and the engine has a variable system to add flexibility to CSS - you can specify several CSS styles as a variable, then just use the variable in the class field of the HTML element you're describing - the browser engine will replace the variable with the several styles on page build. These are written in JavaScript because it's the only language that runs in major browsers. Were other languages available in Chrome, Firefox, etc, this might be better in another language. Websites should be easier to build, faster to load, more robust and stable, while being smaller in memory. But going back to 1997 technology isn't the answer.
• Can_Not 9y ago
  Modern JS frameworks haven't abandoned accessibility. Developers (by choice or by ignorance) are simply not using accessibility features, which is not much different than before JS frameworks. If you're looking for the actual cause and not a cheap scapegoat, it's lack of training and/or MVP culture. Businesses are pushing more and more for getting a prototype out the door and less and less for a quality product.
  • stephengillie 9y ago
    Is there a guide to this which is easily accessible to developers? Are there some quick pointers to make a basic HTML site more friendly to differently-accessing users?
    • ams6110 9y ago
      Test it in a text-mode browser such as lynx, or w3m. If it's usable/readable there, it will probably be fine in a acreen reader, braille, whatever.