Earlier quoted context omitted.
Wow. Which year was it?
In 1993, you could refresh the home page of Netscape (Mosaic) every day and it would mention new sites that had been added. That became unmanageable quickly, which is when two dudes from Stanford started a directory.
First Website (1992)
51–60 of 96 posts
Re: First Website (1992)
#52Earlier quoted context omitted.
In 1993, you could refresh the home page of Netscape (Mosaic) every day and it would mention new sites that had been added. That became unmanageable quickly, which is when two dudes from Stanford started a directory.
I belive that an early beowser, possibly Mosaic, had an edit button. Think of that and the fundamental change of internet philosophy it implies!
Re: First Website (1992)
#53Re: First Website (1992)
#54Sometimes I really miss the pure, text-first web. No popups, no cookie banners, just raw information.
You didn’t have cookie banners because you didn’t have cookies, because there is no need for most websites to have cookies.
Re: First Website (1992)
#55Earlier quoted context omitted.
In 1993, you could refresh the home page of Netscape (Mosaic) every day and it would mention new sites that had been added. That became unmanageable quickly, which is when two dudes from Stanford started a directory.
I belive that an early beowser, possibly Mosaic, had an edit button. Think of that and the fundamental change of internet philosophy it implies!
Re: First Website (1992)
#56Re: First Website (1992)
#57Re: First Website (1992)
#58Ofc these pages cannot replace SPAs. That's not the point. The point is: Much of the web isn't SPAs. And much of what is SPAs shouldn't be SPAs. Much of the web is displaying static, or semi-static information. Hell, much of the web is still text.
But somehow, the world accepted that displaying 4KB of text somehow has to require transmitting 32MiB of data, much of it arbitrary code that has no earthly business eating my CPU cycles, as the new normal. Somehow everyone accepts that text-only informational pages need to abuse the scroll-event, or display giant hero-banners. Somehow, having a chatbot-popup on a restaurants menu-page is a must (because ofc I wanna talk to some fuckin LLM wrapper about the fries they sell!!!), but a goddamn page denoting the places address and telephone number is nowhere to be found.
https://idlewords.com/talks/website_obesity.htm
This talk was given over a decade ago, and its takeaways are as relevant today as thy were back then, and in fact maybe even more so.
Re: First Website (1992)
#59The sad part is, how infinitely more functional these simple, static HTML documents are, compared to much of the shit that floods the "modern" web. Ofc these pages cannot replace SPAs. That's not the point. The point is: Much of the web isn't SPAs. And much of what is SPAs shouldn't be SPAs. Much of the web is displaying static, or semi-static information. Hell, much of the web is still text. But somehow, the world a…
Everyone did accept that because when you needed information from a page that pulls that shit, you don't have a choice, and when you did have a choice, all the others did it too.
Nowadays people just ask ChatGPT for the information they need so they don't have to visit those awful sites anymore.
Re: First Website (1992)
#60to separate chapters: https://timonoko.github.io/alaska/index.htm