How Moore's Law Saved Us From the Gopher Web
Urchin writes "In the early 1990s, the World Wide Web was a power-hungry monster unpopular with network administrators, says Robert Topolski, chief technologist of the Open Technology Initiative. They preferred the sleek text-only Gopher protocol. Had they been able to use data filtering technology to prioritize gopher traffic Topolski thinks the World Wide Web might not have survived. But it took computers another decade or so to be powerful enough to give administrators that option, and by that time the Web was already enormously popular." My geek imagination is now all atwitter imagining an alternate gopher-driven universe.
Even if the Web had been stunted by throttling, the demand for multimedia content would have eventually driven the rise of the Web or at least a super-Gopher.
Javascript + Nintendo DSi = DSiCade
Even if Gopher had dominated due to filtering (a premise I don't agree with), multimedia capabilities would have eventually been added to the protocol out of demand. We'd have the same web we have today.
Yes it was- people went nuts with images on their pages. I even remember one early commentator saying that text-only web pages were actually *better* for people on 14.4k baud modems.
SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
People think that if Person X hadn't been around we might not have Technology Y. Okay, this is based on the idea that somehow Person X has some unique ability and only Person X can create Technology Y. Hate to break it to you, but you're not special. Neither is Person X. Second, the reason we have Technology Y is because we needed it. If those needs haven't gone away, then the pressure to fill that void remains -- and somebody else will come along and fill it eventually. Now you're right that maybe Betamax might have beaten VHS if not for a disturbance in the force, or it would have been HD-DVD instead of Bluray, or whatever... But we'd still have high density optical media. Gopher would have died simply because it didn't meet the needs of the population. Maybe it wouldn't be HTTP that replaced it five, or ten years later, but something like it would have been created.
#fuckbeta #iamslashdot #dicemustdie
"In the early 1990s, the World Wide Web was a power-hungry monster unpopular with network administrators"
As I write this, Firefox is using 300mb of ram and 100% of one core, so not much has changed since then.
Imagine what the Web could be like today, if it had not been for Microsoft's anti-web-standards Internet Explorer and Macromedia's CPU-wasting Flash.
I'm not sure that's right.
The thing is, it's possible to architecturally separate presentation from content from metadata in HTML. Furthermore, people do care about presentation. Who are we to say they shouldn't? The problem is confusing the two.
Here's what I see wrong with the puritanical belief that outlawing presentation hanky-panky will keep the flock virtuously focused on content: people will cheat. When they think they can get away with it, they'll enthusiastically engage in all manner of abominations, like sticking their PowerPoints into gopher collections.
The miserable presentation capabilities of HTML actually did a lot more to promote the very idea that content was something independent from presentation and important in itself. After a bit of straying down the path of unnatural vice (font tags, tables for formatting etc), people discovered they could enjoy their presentation -- no more than that, they could enjoy a wide variety of presentations -- within the blessed institution of stylesheets.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
Isn't there a reason, though? Presumably, using javascript/ajax, you don't need to send/receive as much information (i.e., reload the ENTIRE page) at a time. With plain HTML, you would have to receive a copy of the entire page again... ?
I see no reason why it should take less in normal HTML. Any explanations why you think so?
Stick with linking to the original authors, not the leeches.
What kind of dick says something like that but then doesn't provide the link?
Sounds good to me, gopher don't do flash, right?
Also with lower band-width requirements hosting would be cheaper so banners wouldn't have been a necessity to support the website.
They are.
I still browse with images turned off if I am on a slow GSM connection.
You got a way with words, MightyMartian. I'll give you that. Not many words, but the ones you have you use to great effect.
You are welcome on my lawn.
I founded one of the early online journals before the invention of HTML/HTTP. It's the Chicago Journal of Theoretical Computer Science, providing articles in copy-edited LaTeX source, as well as precompiled PS and PDF.
At first, the journal served papers through anonymous FTP.
Then, I crafted a Gopher structure to make browsing easier.
As soon as HTML/HTTP came along, I created the HTML version of the journal. It was much more maintainable than the Gopher version, because the hyperlinks decoupled the document structure from the file-system tree structure just enough. In a few years, I stopped maintaining the Gopher version, because it required an order of magnitude more work than the HTML, and readers all preferred the HTML anyway.
Adding pictures and stuff is rather trivial for the data architecture, although demanding for the network implementation. With a more maintainable structure, Gopher would have added the extras. It was the Hyperlinks that made HTML work better.
HTML also has some serious maintenance problems, but they appear later when the archive gets large, and they can be addressed with things like PHP compiling and content management systems.
From another point of view: Gopher essentially made file trees visible over the network (which is what I thought I wanted at first). HTML/HTTP provides a crude network database model distributed over the network.
Future advances in data architecture (as opposed to the types of data within that architecture) will have to do with other database models, and with other sorts of commitments between distributed servers, and with looser coupling between data ownership and server ownership. E.g., a way to provide reasonable assurance of future access to a particular data item (access includes being able to find it, not just its existence), without depending on a particular server at a particular registered domain name (the Wayback machine ameliorates the problem, but doesn't solve it).
Mike O'Donnell http://people.cs.uchicago.edu/~odonnell/
I understand your complaint. But to give rendering engine developers some credit, if you really understood the complexities of rendering html properly, you'd understand why they stopped trying to do partial rendering a long time ago, its just not worth the effort at this point.
Can it be done? Of course, is it worth it? Meh, considering most of the Internet is pretty reliable, the amount of times partial rendering would help doesn't really justify diverting that effort from other more important aspects of rendering.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
The difference between HTTP and Gopher has NOTHING WHATSOEVER to do with ability to serve multimedia content, nor with bandwidth. HTTP, or really HTML, just allows more diverse linking patterns than Gopher's hierarchical format. But there's nothing non-graphical or content specific about gopher. I RAN graphical Gopher clients perfectly happily (well, including early Web browsers that supported that protocol.
Buy Text Processing in Python
Thanks, you reminded me of one of my personal "most hated" of the day: The damned butterfly. Anybody else remember that one? It would make butterfly wings on the sides of your cursor and have little fairy dust looking crap trail behind it when your damned CURSOR would "flap its wings"? Always seemed to run into that bastard on the Geocities and that other crap free hosting site that was big in the day....Angel something but the horror of trying to read text as my cursor crapped fairy dung behind my pointer trail has caused me to block it out. If ever there was a fad that deserved a horrible death(if only it would have died quicker!) it was the custom cursor fad!
ACs don't waste your time replying, your posts are never seen by me.