It doesn't do too well: http://oldweb.today/
Found this alarmingly prescient piece on the BBC site from 2000:
http://news.bbc.co.uk/1/hi/sci/tech/874419.stm
'The next generation of mobile phones will make it much easier for the police to carry out covert surveillance of citizens, say civil liberty campaigners.'
Hmm, I wonder how that will play out...
Character encoding issues, nexpected tags, big images all quickly lead to crashes.
Does it though? In 1996 it included a mail client, a news client and a gopher client along with its HTTP & FTP clients. It even had JavaScript back then (I'm just going to take a moment to lament that JavaScript could have been Scheme — I don't even like Scheme as a language for programs, but as a language for web pages and web apps it would have been plenty good enough, even excellent!). It displayed images; it displayed HTML.
Honestly, 1996 was a pretty good year for browsers.
This is precisely the problem the article is about. Why should one application grow 7.5 responsibilities instead of those being in separate applications? It's simply poor design, and now we're stuck with it.
Compare, for example, how VRML worked (entirely software rendering, all the code inside the browser) to how WebGL works (an API to talk to the OS graphics driver, which in turn is just a very fat API on top of the very CISC instruction set of a GPU.)
That's only for graphics programming, mind you; the GPGPU interface is pretty directly representative of the GPU's internal RISC execution strategy.