top | item 47028027 (no title) azangru | 14 days ago > The browser ... wasn’t architected to run applications.Could you explain this? What prevents the browser from running applications? How should it have been architected otherwise if running applications was the goal? discuss order hn newest zahlman|14 days ago I think the idea here is that the DOM was designed as a model for document presentation, not for GUI layout. krapp|14 days ago The DOM was designed as a model for hypertext document presentation. That document already is an application. Hyperlinks already are a GUI.And 99% of what people here consider "web applications" are just documents meant to be read as documents that have any javascript in them at all.This whole "document vs app" dichotomy is mostly a fantasy.
zahlman|14 days ago I think the idea here is that the DOM was designed as a model for document presentation, not for GUI layout. krapp|14 days ago The DOM was designed as a model for hypertext document presentation. That document already is an application. Hyperlinks already are a GUI.And 99% of what people here consider "web applications" are just documents meant to be read as documents that have any javascript in them at all.This whole "document vs app" dichotomy is mostly a fantasy.
krapp|14 days ago The DOM was designed as a model for hypertext document presentation. That document already is an application. Hyperlinks already are a GUI.And 99% of what people here consider "web applications" are just documents meant to be read as documents that have any javascript in them at all.This whole "document vs app" dichotomy is mostly a fantasy.
zahlman|14 days ago
krapp|14 days ago
And 99% of what people here consider "web applications" are just documents meant to be read as documents that have any javascript in them at all.
This whole "document vs app" dichotomy is mostly a fantasy.