News for hackers. Stuff that matters.

A comment on A Look Back at the 1960s PLATO Computing System. Parent comment

Re:A Look Back at the 1960s PLATO Computing System by lkrubner on Monday March 19, 2018 @09:56AM (#16618350)
The deeper problem is that the tech industry is slow to get rid of HTML, even though HTML was created to exchange documents, and nowadays we mostly use it as a GUI for network software. See "The Problem With HTML":

http://www.smashcompany.com/technology/the-problem-with-html

[ Parent | on HN ]
Re:A Look Back at the 1960s PLATO Computing System by lmm on Monday March 19, 2018 @10:21AM (#16618485)
HTML isn't the problem - declarative markup is a great way of doing GUI layout, non-web GUI frameworks tend to come up with alternatives that look similar. The problem is CSS, which is a fractal of bad design, broken at every level, from selectors to the box model.
[ Parent | on HN ]
Re:A Look Back at the 1960s PLATO Computing System by Retric on Monday March 19, 2018 @11:34AM (#16619177)
CSS works fine for Text markup. The problem is you get two models one where the Browser picks where stuff goes depending on the browser and local settings, another where the designer makes that choice. You can't have both things exist at the same time, on top of that most designers don't know what they are doing.
[ Parent | on HN ]
Re:A Look Back at the 1960s PLATO Computing System by pjmlp on Monday March 19, 2018 @10:36AM (#16618615)
That I agree with.

Android, iOS, XAML and QML are quite nice to work with.

[ Parent | on HN ]
Re:A Look Back at the 1960s PLATO Computing System by ahartmetz on Monday March 19, 2018 @10:14AM (#16618448)
It used to be conventional wisdom that using HTML as a layout system is wrong, you know. Because it wasn't meant to be one, and text content was supposed to be independent of the medium on which it is viewed. Well, at the time I had my doubts that it was going to work, but it was (and still is) a nice idea.
[ Parent | on HN ]