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.
> Service Unavailable
> The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Plus the demo videos don't work on Firefox in Windows 10, and there's no screenshots or any other form of seeing the demo.
It appears one of the links in the article is wrong.
The correct link is: https://worldwideweb.cern.ch/browser
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.
Just kept loading and didn't ever deliver the thing I was waiting to see.
Yep, definitely makes me nostalgic for the early web.
For those of you having trouble getting it to load while it's being hugged to death, I took a properly meta screenshot:
We're (the team) are waiting to hear from the Ops folk at CERN to get the server to stop 503'ing. Until then, you can try it out above.
wikipedia has it https://en.wikipedia.org/wiki/WorldWideWeb#/media/File:World...
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.
And isn't web assembly a further step in the same direction?
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.
Just my 2 cents.