I remember that. A few weeks later ran a script to count all the websites on the Internet.. 324 at that time.
The line mode [1] made me pause. Not because you can do anything too useful (most of the cool links are dead, or telnet) but because it seems like a really cool place to explore, learn, and hack.<p>No ads, no random tits, nobody trying to convert you to their politics, trying to scam you, or telling you to kill yourself. Just people sharing interesting things.<p>Really makes me excited for the internet until I close the tab.<p>[1] <a href="http://line-mode.cern.ch/www/hypertext/WWW/TheProject.html" rel="nofollow">http://line-mode.cern.ch/www/hypertext/WWW/TheProject.html</a>
It just blew my mind! I suppose I shouldn't be surprised at all, JS was written for manipulating the DOM but I was NOT expecting a cool terminal style with a typing/Matrix-style transition animation from some of the first webpages ever.<p>My brain even ascribed a CRT distortion effect to it, even though that's not actually happening.<p>edit: okay, no, I am an idiot. Those pages were made in 2013:<p><a href="https://line-mode.cern.ch/" rel="nofollow">https://line-mode.cern.ch/</a>
A little later, but I have a key chain from a dealership that has their website advertised on it, they didn't have a domain name so it's advertised as <a href="http://123.123.123.123/web.htm" rel="nofollow">http://123.123.123.123/web.htm</a>
Yeah, I made a website as part of a class at BCIT in 1995 and we just had a raw IP so I was showing people my awesome website on <a href="http://142.232.162.27" rel="nofollow">http://142.232.162.27</a> (actual IP) every chance I got.. for all like, 2-3 some-odd people I knew who had computers and had internet access. Luckily I quickly thereafter got a Geocities site which was just a little easier to remember/share lol
It’s impressive how quickly the WWW became mainstream, given how few people had internet access back then. Bitcoin is now 16 years old but compared to the WWW in 2008 is hardly used on a daily basis.
Fascinating reading if you care about system design. Who would imagine this charged the world.<p><a href="https://info.cern.ch/hypertext/WWW/DesignIssues/Overview.html" rel="nofollow">https://info.cern.ch/hypertext/WWW/DesignIssues/Overview.htm...</a>
When this was first created, how did people usually navigate back to the previous page? I notice there are no "previous" or "home" links here. Was there a "back" button/key, or would you have to edit the URL directly?<p>Edit: Answered my own question I think. If you choose the option to browse "using the line-mode browser simulator", you can literally type in "Back" to go back.
This site has a way to experience as it once was. I’m on mobile now, but from what I remember when I tried it, each link opened up a new document window. So the idea of going back wasn’t relevant. You’d simply close the window.<p><a href="https://worldwideweb.cern.ch/" rel="nofollow">https://worldwideweb.cern.ch/</a>
We used telnet. There were no graphics per se. Before www the "interactive" internet was gopher and wais and co.<p>Navigation was moving a cursor around to highlight points of interest, some of which would be links to further stuff or controls to do something like go back or forwards.<p>Install lynx or links2 (ie text mode browsers) and you'll get the idea.<p>The vaguely graphic efforts with browsable content that you might recognise before www were the likes of Compuserve. That got you a sort of forum style interface.<p>It's quite hard to explain just how fast things have moved over the last 40 odd years (I'm 1970 to date - 55). I should also point out that my granddad saw rather a lot of change from 1901 to 1989. To be honest the last 15 odd years are even madder than the previous 25 and that's just my own personal recollection.
It looks like you can also shorten "Back" to "b".<p>So far, I like this line-mode browser simulator much more than what is commonly available for the command line (lynx or links2). Does any one know of a modern implementation of it? (Where links are numbered instead of the user having to navigate around the document).
Ugh, memories. I'm so old my first web browser was Mosaic and I think I saw this. I used a provider called Texas MetroNet that served up dial-up PPP connections for $45 a month on a speedy 28.8K baud modem. Days of wonder, I tell ya.<p>New days of wonder seem to be ahead, though. That said, there's about 100X more angst involved these days.
1992 seems a bit late. Wasn't this first website put online on 20 December 1990?
This was in Gopher first, where you had to click a link to view a picture. Then I heard about Mosaic, where you can have pictures and text on the same page. Some problems emerged, until I learned you use <p> to separate chapters: <a href="https://timonoko.github.io/alaska/index.htm" rel="nofollow">https://timonoko.github.io/alaska/index.htm</a>
Sure, but have you heard the Eurovision Song contest entry about the web: <a href="https://www.youtube.com/watch?v=Zc9quuVYZF4" rel="nofollow">https://www.youtube.com/watch?v=Zc9quuVYZF4</a>
Sometimes I really miss the pure, text-first web. No popups, no cookie banners, just raw information.
Has anyone been able to recover the original source code? The README here: <a href="https://info.cern.ch/hypertext/README.html" rel="nofollow">https://info.cern.ch/hypertext/README.html</a> mentions a src/ directory under the same location but it 404's to me.<p>Would love to see the source for the original httpd.
Maybe here you'll find what you are looking for: <a href="https://www.w3.org/Daemon/" rel="nofollow">https://www.w3.org/Daemon/</a><p>Though you can browse and download the latest version 3.0A (1996), there is a directory where they have older versions, but its a bunch of files mixed up with different versions. <a href="https://www.w3.org/Daemon/old/" rel="nofollow">https://www.w3.org/Daemon/old/</a>
I've come across this before, one thing I haven't realized is that in addition to an emulator of the line browser, they're also offering an emulation of the original NeXT browser WorldWideWeb:<p><a href="https://worldwideweb.cern.ch/" rel="nofollow">https://worldwideweb.cern.ch/</a><p><a href="https://worldwideweb.cern.ch/browser/" rel="nofollow">https://worldwideweb.cern.ch/browser/</a>
Xanadu<p>Ted Nelson's dream since early `60s: all the world literature in one publicly accessible global online system (analogy: you can today get a telephone link from anywhere to anywhere, so why not from any text to any other?). Every reference to a text will lead to royalties being paid automatically to the author. Autodesk, (the makers of AutoCAD) will produce a product "real soon now". Includes the use of full versioning (claimed to be horrifyingly complex), "hot links" (called transclusions) and zippered texts (eg. parallel texts like for translations or annotations.)
It reminds me of a fun fact: HTTP/0.9 websites are the fastest because they were created years ago and have simple content.
On university campus when our student dorms got internet wired, we first got Gopher, and I remember - because it was hard to follow all these technology developments - that the web was like 'suddenly' there, and we started surfing. Everyone making the switch. Early pages were often copies of their Gopher equivalents.
At least partially down at the moment, but it's super fun looking through their service status board. I <i>love</i> little glimpses into other people's worlds. <a href="https://cern.service-now.com/service-portal?id=service_status_board&area=IT" rel="nofollow">https://cern.service-now.com/service-portal?id=service_statu...</a>
The sad part is, how infinitely more functional these simple, static HTML documents are, compared to much of the shit that floods the <i>"modern"</i> web.<p>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 <i>shouldn't be</i> SPAs. Much of the web is displaying static, or semi-static information. Hell, much of the web is still text.<p>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.<p><a href="https://idlewords.com/talks/website_obesity.htm" rel="nofollow">https://idlewords.com/talks/website_obesity.htm</a><p>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.
> Somehow everyone accepts<p>Everyone <i>did</i> 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.<p>Nowadays people just ask ChatGPT for the information they need so they don't have to visit those awful sites anymore.
Some of the stuff we have been adding since then is GOOD though.<p>Some examples:<p>We now have to accommodate all types of user agents, and we do that very well.<p>We now have complex navigation menus that cannot be accessible without JavaScript, and we do that very well.<p>Our image elements can now have lots of attributes that add a bit of weight but improve the experience a lot.<p>Etc.<p>Also, things are improving/self-correcting. I saw a listing the other day for senior dev with really good knowledge of the vanilla stuff. The company wants to cut down on the use of their FE framework of choice.<p>I cannot remember seeing listings like that in 2020 or 2021.<p>PS.<p>I did not mean this reply as a counterpoint.<p>What I meant to say is, even if we leave aside the SPAs that should not be SPAs, we see the problem in simple document pages too. We have been adding lots of stuff there too. Some is good but some is bad.
> We now have to accommodate all types of user agents, and we do that very well.<p>Simple websites don't even care about the UA.<p>> We now have complex navigation menus that cannot be accessible without JavaScript, and we do that very well.<p>Is there an actual menu which is more than a tree? Because a dir element that gets rendered by the UA into native menu controls would be just so much better.
Not bad PageSpeed scores for the first site:<p>Performance: 100
Accessibility: 86
Best Practices: 92
SEO: 90
In the mid 70's, I was a graduate CS student at USC's Information Sciences Institute. I remember my feeling of awe when I used Arpanet (or was it Darpanet) to log into London and do stuff there. Wow!
This is great. I particularly enjoyed this entry in the FAQ about how to find web pages: <a href="https://info.cern.ch/hypertext/WWW/FAQ/KeepingTrack.html" rel="nofollow">https://info.cern.ch/hypertext/WWW/FAQ/KeepingTrack.html</a><p>> When (s)he has found an overview page which (s)he feels ought to refer to the new data, (s)he can ask the author of that document (who ought to have signed it with a link to his or her mail address) to put in a link.<p>> By the way, it would be easy in principle for a third party to run over these trees and make indexes of what they find. Its just that noone has done it as far as I know
I really like how different and the same the html tags are.
I love that there is no attribution. Says a lot about the concept of collaboration and know sharing in those early days.
how did we go from this to nextjs?
There's a difference between document-based web sites like this one and web applications. The potential for web applications has mostly emerged as a side effect of the introduction of JavaScript. Back then, JavaScript was supposed to only add minor enhancements to web sites.
Well... Right here on the the very first website Tim Berners-Lee talks about how to build interactive web applications (here called "gateways"), albeit server-side rather than client-side:
<a href="https://info.cern.ch/hypertext/WWW/FAQ/Server.html" rel="nofollow">https://info.cern.ch/hypertext/WWW/FAQ/Server.html</a>
Money. Ruins everything. And also enables. So it's a win/lose situation.
I appreciate the HTTPS support
Still faster than most websites
Banned in UAE (at least on DU)
Ah, fond memories... First website in Poland was the homepage of the Faculty of Physics of the Warsaw University (been there at that time). It was 1993 I think, although wayback machine stores a newer snapshot (1998), but it looks the same as original page: <a href="https://web.archive.org/web/19980120060239/https://www.fuw.edu.pl/" rel="nofollow">https://web.archive.org/web/19980120060239/https://www.fuw.e...</a>
declaring a website to be "first" introduces a definitional problem.<p>to put it in terms of a simple example, you need several HTML pages before one of them can link to another, but so far that's just hypertext. then you need pages spread out across plural sites to be able to create a web.
I found it via gopher and wais - I can't remember which one did what, it was a fair few years ago.<p>I telnetted from my PC to a VAX, then to a X.25 PAD, then onto a Janet system, then to somewhere in the US and then to CERN. Eventually I'd get a menu with a link to the www. I'd then navigate the www with different keystrokes.<p>www was/is free form links to stuff instead of hierarchical menus. It was an evolution not a revolution and there is no need to invoke "chicken or egg".
Related:<p><i>CERN rebuilt the original browser from 1989 (2019)</i><p><a href="https://news.ycombinator.com/item?id=47095429">https://news.ycombinator.com/item?id=47095429</a>
A (1992) copy.<p>Website about this project: <a href="https://first-website.web.cern.ch/" rel="nofollow">https://first-website.web.cern.ch/</a><p>Some previous discussions:<p>6 months ago <a href="https://news.ycombinator.com/item?id=45125239">https://news.ycombinator.com/item?id=45125239</a><p>2024 <a href="https://news.ycombinator.com/item?id=40177906">https://news.ycombinator.com/item?id=40177906</a>
Everyone in silicon valley would do well to remember why the web was built (by other people, elsewhere).
[dead]
[dead]
[dead]