[thaumasiotes]

> It would be nice if there was a standard that existed allowing authors to simply write documents, saving them as models. Then, each device could read from a standard model file and, using custom controller code, generate a view displaying the text/images optimized for its display.

This standard is called "HTML". What you describe is the entire idea of HTML. Frankly, it's embarrassing that a web browser presented with a long stream of text won't keep the line lengths capped at a reasonable length.

[uglycoyote]

Yes, this is why it drives me crazy that Safari on iOS does not wrap text as you zoom in. Every browser since the beginning of time has been able to properly wrap the text as you increase the text size, and Apple has totally broken that.

[kalleboo]

That was one of my biggest complaints about iOS coming from Android. Reading Hacker News comments on iOS is a horrible experience of swiping back and forth, back and forth.

[Joeri]

What's worse is that the other browsers decided to emulate this bad behavior. Most of the mobile browsers now no longer properly wrap text when zooming, where once they did.

[dgallagher]

I guess you could say that HTML meets that standard. For example, <h1> through <h6> headers could be rendered by the browser accordingly; most default renderers still display things mostly the same way Netscape Navigator 2.0 did back in the Win 3.1 days (disable CSS on a site and you'll see).

Marked on the Mac, which is a Markdown renderer, loads .mmd files and renders them against a CSS template which you can swap out. That fits the MVC idiom nicely, although far from a perfect implementation as it's merely meant for viewing markdown files, not everything on the internet.