Realization
2013-03-12 19:26:09.487944+00 by Dan Lyke 3 comments
Realization: "Web 2.0" is "WWW II". Where's the Internet's Normandy? It's time to take back metaphorical France. #tablesruinedeverything
2013-03-12 19:26:09.487944+00 by Dan Lyke 3 comments
Realization: "Web 2.0" is "WWW II". Where's the Internet's Normandy? It's time to take back metaphorical France. #tablesruinedeverything
[ related topics: Net Culture ]
comments in descending chronological order (reverse):
#Comment Re: made: 2013-03-13 12:00:23.509551+00 by: meuon
Because I build "applications" using a web interface, a little bit of ajax is a good thing. It is very useful for lookups into large sets of data that you would not want to have in drop downs.
The problem is when it is used for everything, especially things it should not be used for. jQuery and like made async javascript and web layout the brainless bitch of the clueless.
And once the users have seen pretty shiney clicky things, they demand it everywhere.. while complaining that the pages take seconds to render.
I'm watching some of our main applications web pages with a sniffer, and am proud that most pages are still < 10kb and work well (even with a lot of information on them) on nasty cell and satellite connections. In my work world the users have crappy computers and crappy network connections. Traditional web works very well in those places.
#Comment Re: made: 2013-03-13 04:47:40.61419+00 by: Dan Lyke
Yeah, but so did divs and spans. When we let HTML become a rendering language rather than a markup language, dropped the semantics for the display... well... yeah.
But agreed: If you had to draw a line in the sand, AJAX is probably the best place to point to and say "that's where the web died".
#Comment Re: made: 2013-03-13 03:52:49.006574+00 by: spc476
I would say that AJAX ruined everything—the idea of making a webpage an application.