But it makes sense it is a GUI browser since it was developed on a NeXT
I'm having trouble pinning down when WorldWideWeb got inline image support, but based on https://www.w3.org/History/1991-WWW-NeXT/Implementation/Feat... I'm guessing sometime between 1992 and 1994, when there are screenshots with inline images, so maybe after Lynx was published.
https://www.themarginalian.org/2014/07/18/les-horribles-cern...
I was also disappointed that the editing went away after the first browser. (There was "Amaya" which had editing, but it was a research thing and not a commonly used browser.)
The original source code isn't really involved, which is a shame, since it is actually available.
IMHO this should have been (something along the lines of) GNUstep + TimBL's original code (mirror: https://github.com/cynthia/WorldWideWeb) + Emscripten + getting Emscripten to work with ObjC. Now, that would have been cool.
This is the most commented HN posting on this from that time (2019):
The performance would likely be comparable %)
:-)
tylerdane•2h ago
Kim_Bruning•56m ago
Something was lost along the way.
(Nowadays you need a separate wiki engine on a site to be able to do that)
krapp•52m ago
I don't think a web where every page is globally editable by default would be a good idea, but I can't imagine at all how it would work without a backend, unless all of the changes are just local. But that seems pointless.
actionfromafar•43m ago
zabzonk•42m ago
Making notes for your own consumption?
Kim_Bruning•42m ago
shakna•6m ago
The user makes a request, and then does whatever they like with the answer. Not just whatever is sensible, but whatever they want to do.
If that concept somehow became accepted again... I think the accessible web might well become a solved problem, rather than an endless slog.
karlgkk•11m ago
No you don’t. These browser simply PUTs the request and your web server simply edits the document. Versioning is optional, of course.