> Even though the browser would guess MIME types based on filename, HTTP didn't have MIME types until HTTP 1.0
correct
but guessing the mime type is what many tools still do today
MIME types were one of the (many) emergent features added to HTTP out of necessity
like, for example, HEADERS
HTTP/0.9 had no headers, no status code it was basically nothing more than
- GET THAT
- HERE IT IS ITS RAW CONTENT
But Lee HyperMedia browser had support for different file types because he already envisioned it as a mean to browse a "web" of hosts in search of "resources of different kind"
WWW was text only the same way Excel was text only, meaning they could not show text and images side by side, not in the sense "VT100 text only"
Ask you this: was there another software that let you click on a link representing a file on another computer possibly on the other side of the planet, download it and show it to you in (almost) real time?
This [1][2] is the best Microsoft could do using all its resources in 1990, on a platform that was already very advanced for graphics (Word 1.1 for Windows looks like sh*t), T.B.Lee was basically himself writing the code for the server, the client on a platform that was still in its infancy while also having to learn the framework (NeXTSTEP)
[1] https://www.versionmuseum.com/images/applications/microsoft-...
[2] https://www.versionmuseum.com/images/applications/microsoft-...
> or the page you posted is wrong about what NeXtStEp could support in 01990.
you can check by yourself by buying (or downloading) a copy of the manual
https://findingaids.library.cmu.edu/repositories/2/archival_...