3 ms·
Sometimes I think back and ask myself if all of this progress in web standards has really got us anywhere. What can we do now that couldn't be done 20 years ago
by colechristensen 13y ago
Sometimes I think back and ask myself if all of this progress in web standards has really got us anywhere. What can we do now that couldn't be done 20 years ago (putting aside connection speed) and is all of this progress really worth the trouble.
It makes a person want to start over, from scratch while keeping it simple adding as little as possible. Of course something like that would have to be done extraordinarily well to be worth it at all to avoid https://xkcd.com/927/ https://xkcd.com/927/
- pjmlp 13y agoIt just made us lost the sense where to go, by re-inventing, badly, what was already possible on the desktop with Hypercard and similar systems.
- dasil003 13y agoIt's a nice dream, but even if you had that power to go back and time you'd probably just make other mistakes. There isn't an intelligence capable of designing big open standards like the web, rather they only move forward by natural selection, much like terrestrial life has. In the end I think we've gotten some pretty remarkable things this way, remember before the web there was no such thing as cross-platform, instantly-available globally, and accessible to any person with any disability multimedia. Few people seem to recognize how much of an accomplishment this is: http://www.youtube.com/watch?v=uEY58fiSK8E http://www.youtube.com/watch?v=uEY58fiSK8E
- yuhong 13y agoYea, that is why WHATWG HTML is a "living standard". In fact, I am thinking that even the "HTML5" buzzword is a misnomer.
- stoptalkingshit 13y agoNope. What has happened is a remarkable idea has fallen into the hands of baboons, who promptly bungled the implementation completely. And now we have this myth that it has to "evolve" because for years some people missed the OBVIOUS. Welcome to the future of shamanistic computing: blood-cooled CPUs, integrated ouija boards, USB incense burners...
- clarry 13y ago> There isn't an intelligence capable of designing big open standards like the web I think the problem here is big. How about small standards with a limited scope? I don't want these huge standards that take millions of lines of code to implement.
- dasil003 13y agoThat's exactly what the web is! It's made up of hundreds of such small standards plus thousands of ad-hoc implementations, solutions, and deep supporting infrastructure. Again, the point is it's too big to be designed.
- clarry 13y agoYes exactly, too big is exactly what it is. And my point was that it could be small. In practice of course we'd never even agree on a definition of what the web is or what it should be, so even the idea of designing a compact standard for it is hopeless.
- seagreen 13y agoWe have gotten somewhere -- the web has become a decent program delivery system. In the process it's degraded pretty badly as a document delivery system. If you start over I recommend separating those two projects.
- nandhp 13y agoWell, we tried that for awhile. The web was mainly good for documents and if you had a program it was done with Flash. And then people were making websites entirely in Flash. And then people realized that was a bad idea because Mobile, and everything got better. Until the App Store came along. Fine, so now program delivery has been separated from document delivery, but every document provider that used to just be a website now requires you to use a special program from the App Store instead of using a web browser or some other generic "document viewer". Or, at the very least, you have to tell them you don't want it every time you visit their website. The problem isn't that the web is a bad document delivery system -- it's not. The problem isn't even that the web is just as good at delivering programs as it is at delivering documents. The problem is that there are a large number of people who know nothing about best practices and are way too enthusiastic about making things look flashy. They create documents and they don't care how you want them to look. If that means they have to create a Program instead of a Document, that's fine with them.
- keeshawn 13y agoDownload our app, and let us read your entire contact list and send out SMS messages as you, and read and post to Facebook as you, and do whatever else we want to anything for any reason. (Accept)
- kmfrk 13y agoCSS has always been a hack, and the web we have today as a result of competing browser rendering however the hell they want based on their popularity - and the popularity of any co-developed devices - is just about the only thing that can make me countenance communism as a web developer. Having said that, it's possible that we might be in for a second era of webdesign, as MS retire support of XP and the browsers that have dragged down web development.
- morbius 13y agoThis site actually chronicles the terribleness of the modern web quite perfectly. Warning: NSFW. http://motherfuckingwebsite.com http://motherfuckingwebsite.com
- sequence7 13y ago> Sometimes I think back and ask myself if all of this progress in web standards has really got us anywhere. > What can we do now that couldn't be done 20 years ago (putting aside connection speed) and is all of this progress really worth the trouble. Well let's see if we can make a short list: 1) Can I look up almost anything? Yes [0] 2) Can I learn a foreign language for free? Yes [1] 3) Can I fund something interesting? Yes [2] 4) Can I communicate with my family and friends for free? Yes [3] 5) Can I learn stuff for free? Yes [4] Seriously I didn't even try, yes progress has got us somewhere. Admittedly we do now have n+1 standards [0] http://wikipedia.org http://wikipedia.org [1] http://duolingo.com http://duolingo.com [2] http://kickstarter.com http://kickstarter.com [3] Honestly there are so many - email, skype, facebook, whatsapp, etc ... [4] http://khanacademy.com http://khanacademy.com edit - edited
- colechristensen 13y agoWhich of those wasn't possible in 1995 with a modern Internet connection? I posit that everything you describe would have been entirely possible with a little less polished appearance 15-20 years ago and that there could be real strong value in starting over and keeping things simple.
- hippee-lee 13y agoDuolingo - because it's not just me learning Spanish, it's us translating English only websites to Spanish. Perhaps I'm not versed enough in the services available in '94 - I didn't really start to use the internet much until college when I got access to the computer labs. Was there something like it around then? I say this because the most impressive thing to me about duolingo ( and the captcha system designed by its founder before it ) is the efficient way to leverages different individual goals to aggregate really large differences for both individuals. Ie the person wanting to learn a new language for free and the person with an English only website that needs to get it translated into multiple languages.
- saurik 13y agoI presume the point is not what was already built but what was possible: Wikis have existed for a very long time, and nothing about Wikipedia seems difficult to do with very old versions of Netscape.
- jedrek 13y ago> What can we do now that couldn't be done 20 years ago (putting aside connection speed) and is all of this progress really worth the trouble. Well, I know your 20 years is hyperbole, but let's see: 1) We can display video and play sounds. We can do it using native browser controls now, but in 1994 you couldn't do it at all - plugins weren't introduced until Netscape Navigator 2.0 which came out a year later. 2) We can display updated data without reloading the entire website. This let's us do stuff like chat or use collaborative tools. 3) We can disassociate content from styling, so styling data can be transmitted once and can be changed en masse with ease. 4) Cookies showed up 19 1/2 years ago, so you wouldn't be able to store user login data without it showing up in the URL - it makes sending URLs to other people very awkward. 5) Oh wait, you wouldn't be able to log in because forms weren't in the HTML spec yet, HTML 2.0 didn't come out til 1995. 6) We can actually... do layouts of web content. Tables didn't come around til HTML 3.0. The initial version of the web was pretty much a prettier version of Gopher - with some inline graphics and styling. This site in would not be able to exist in 1994, unless you wanted to submit comments via email?