|
|
|
|
|
by mhd
5550 days ago
|
|
It's at times like this when I think that we should seriously reconsider the current browser model. We've reached a point where there's a lot of complexity in the system and we're mostly paying lip service to the original idea of presentation-independent content. And the vestiges of that idea are keeping us back. If you want something accessible with a "modern" JavaScript-based web application, you're almost bound to rewrite most parts of the interface for a pure HTML version, if at all possible and/or desirable. Quite often less effort than jumping through hoops to have something that degrades gracefully. Now I think this will only get worse. At one point in time, it might be better to regard HTML as the Gopher of its time and consider a next step. Probably won't ever happen, as the sheer ginormous size of the "legacy" web makes any endeavors in this direction almost futile. Does anybody remember PostScript-based GUIs? We're throwing a lot of barely-connected ideas and syntaxes into a browser to emulate NeWS/DPS -- poorly. |
|