Something that I couldn't find much information on.. How exactly did the editing work? Could I edit a file and then once I'd saved the changes whoever went to the file next would also see my edits?
How did this all work? For me, this is absolutely fascinating and I guess in some ways this reminds me of modern wiki software (especially something like vimwiki that I use daily).
If anyone has some 'technical' resources about how this browser worked, I'd love to read it.
PUT, DELETE, etc were part of HTTP/1.1. The WorldWideWeb browser (later called Nexus) was created during the time of HTTP 0.9 (or rather the versionless HTTP).
I spoke to a few of the people involved in the original 1990s project and one big issue was authentication into servers was way too complex.
The simulation (I wrote the JavaScript for it), writes to local browser storage (IndexedDB), the original WorldWideWeb would write to disk (networked or local).
I was able to get it to load after a few tries, and I'm pleasantly surprised at how well it handles the formatting of some of my sites. It seems to do okay with text, though it doesn't seem to support images or form elements; I haven't been able to attempt a login.
For those of you having trouble getting it to load while it's being hugged to death, I took a properly meta screenshot:
i suppose this is a simulation of the WorldWideWeb browser... i think in very old times you could find this in some linux distros along with another browser with an italian sounding name. i think u can find screenshots in google
That was an evolutionary dead end that didn’t persist; since every other browser that followed focused on retrieval and display, not editing, they didn’t need to distinguish between “follow this link” and “open this link for editing.” (To be fair, given the lessons of SGML, there wasn’t any reason to think folks would just open up vi or emacs and start editing markup, so they get a pass on the UX for that one.)
Javascript isn't required for everything, and nothing is stopping anyone from writing simple, static sites without it.
The web was always envisioned to have potential beyond just static hyperlinked documents. The belief that everything beyond basic HTML has been a corruption of an ideal rather than evolution is a confabulated view of history, brought on mostly by nostalgia and a frustrated sense of elitism now that the web is as mainstream as any other form of mass media.
I dont have an issue with pushing beyond pure html. But js doesn't build on that concept of xml and work along side of it. JS destroys that concept and replaces it with something unique on every site.
I think web assembly is a step in the right direction and the sooner we drop js the better.
I don't think that's entirely fair. Javascript's original intent was to allow scripting the DOM and adding interactivity to the document, which could be considered working alongside it.
I would agree that the scale of its use has been taken too far, but that seems more a complaint about implementation and developer culture than the language itself. Even without Javascript, the design of every site is still potentially unique.
And isn't web assembly a further step in the same direction?
I don't think allowing scripting of the DOM was a great idea personally. The goal of the original web was layout and structure of information and the links between them.
Javascript bulldozes over both the DOM and URL's.
The nice thing about web assembly from what I've read, is that it doesn't allow access to the DOM. It basically creates its own sandbox that is then included on the page.
You can INCLUDE interactivity in the page, but, you can't overwrite the page itself.
Because of this it kind of encourages a progressive web design style. You will design the html/xml first then you will wrap the interactivity within.
This will encourage a separation of concerns between highly interactive, more complicated code, and layout and structuring of documents.
There will be some issues to be overcome and I doubt it will be as ideallyic as I imagine, but I think overall it would be a more sane web being able to select 'disable javascript' without any worries.
How did this all work? For me, this is absolutely fascinating and I guess in some ways this reminds me of modern wiki software (especially something like vimwiki that I use daily).
If anyone has some 'technical' resources about how this browser worked, I'd love to read it.