4 ms·
You're kinda proving my point for me there. The only upside you actually identified there, is a reduced number of requests, which is already possible by using
by stephenr 12y ago
You're kinda proving my point for me there.
The only upside you actually identified there, is a reduced number of requests, which is already possible by using HTTP Keep Alive and HTTP Pipelining.
- kragen 12y agoI was just explaining why the downsides you were writing about weren't serious. I didn't devote much effort to explaining the upside. I guess that a lot of things that seem obvious to me aren't obvious to you, probably because you haven't spent much time thinking about them. I'll try to do better: 1. You can use 10MB of widely-used JavaScript and stock icons on your web page, and the browser will be able to see the page after downloading 100K instead of 10MB. HTTP keepalive and pipelining don't help at all with that. 2. There are no more broken links, so people can link to stuff that isn't hosted on their own server without fear that it will go away next year, or be redirected to more commercially remunerative content, such as linkspam. (This is conditional on them caching a copy on their own server, of course.) HTTP keepalive and pipelining don't help at all with that. 3. Resources can be cached close to you on the network without you having to trust the cache not to feed you corrupted versions of them. (You do have to trust the cache to not report you to the feds for reading an article about how to download Interstellar.) This makes a huge difference in page load time by reducing latency. Again, while HTTP keepalive and pipelining can reduce the multiple of latency, they can't reduce the latency below 2×RTT to the origin server, and practically speaking they're limited to several times that. This is especially important if you're trying to host your personal pages on a high-latency residential internet connection, and/or browsing from a high-latency country. 4. Making every website not just archivable but also forkable enables a new kind of lightweight collaboration. Well, not totally new — I mean, we're doing it now on GitHub and, in a different form, on Wikipedia. 5. Naming web pages by hash rather than by IP address or by a DNS name that maps to an IP address makes it easy to host them on dynamic IP addresses, including with transparent failover when one of them goes down for a while.
- stephenr 12y agoCDN's already solve #1 and #3 #2 is no different than mirroring content, e.g. how fireballed.org works, but over longer time. #4 collaboration is about working on something together. Every visitor to your site is unlikely to need/want/care about collaborating on it. #5 You're suggesting an SHA1 hash is easier to remember than a domain name? Seriously?
- kragen 12y agoThis "X is no different than Y/X already solves Y" conversation reminds me of thinking, around 1992, that clicking on a link to a page on another web site was "no different than" connecting my FTP client to a new FTP server, logging in, cding to some directory, and downloading and viewing a file from that directory. In some abstract sense, yes, they're the same thing; but in terms of human experience, they're very different. You ask, "You're suggesting an SHA1 hash is easier to remember than a domain name? Seriously?" Consider that if I seem to be saying something that's obviously ridiculous, even to you, then maybe you've misunderstood what I was saying, as in this case. I'm going to give you the benefit of the doubt and assume that your lack of understanding is genuine, not feigned to give you an excuse to be rude, but you were rude anyway.
- stephenr 12y agoYou suggested Git based web page hosting would allow for local mirrors of content so they are available regardless of the availability of the original site. I told you that is already happening in practice, without the overhead of Git. in your example, i would not agree those two things are the same. Clicking a link that goes to a http:// http:// url and clicking a link that goes to the same file via ftp:// i would say are reasonably similar for the end user. you're right, i didn't read into #5 enough. so for the purposes of "easier dynamic ip hosting" you're suggesting that browsing to a sha1 hash means it can come from any computer that has a copy of it? but nobody is going to remember hashes. so you need to use dns or similar, so say "foo.com" has a GIT record, the value of which is an sha1 hash.. but then the client needs to find somewhere to get that from... so presumably you're suggesting some kind of peer to peer system for hosting? and all of that is somehow better than the existing model, where you simply have a DNS server that has an api to update the IP address of an A record quickly? You've also skipped over a big issue here.. this whole concept relies on a website being nothing more than static files. It also effectively removes the ability for the author to have any idea at all about how many people view his site. Git is reasonably good at what it does. It has some flaws but for versioning text based content, and fostering collaborative working amongst developers/authors, its a reasonably good solution. As a replacement for HTTP web pages, caching proxies, CDNs, parts of DNS? not so much.