Comments on: Breaking the Web http://gojko.net/2007/03/22/breaking-the-web/ Building software that matters Thu, 02 Feb 2012 07:12:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: links for 2007-03-24 « B-link List http://gojko.net/2007/03/22/breaking-the-web/comment-page-1/#comment-4417 links for 2007-03-24 « B-link List Sat, 24 Mar 2007 00:54:33 +0000 http://gojko.net/2007/03/22/breaking-the-web/#comment-4417 [...] Gojko Adzic » Breaking the Web Leaving behind the traditional ‘request-wait-reload page‘ processing, Web 2.0 broke many boundaries and brought online applications and sites much closer to an interactive desktop, but best practices from the desktop model have still to penetrate int (tags: programming web ajax) [...] [...] Gojko Adzic » Breaking the Web Leaving behind the traditional ‘request-wait-reload page‘ processing, Web 2.0 broke many boundaries and brought online applications and sites much closer to an interactive desktop, but best practices from the desktop model have still to penetrate int (tags: programming web ajax) [...]

]]> By: Russ http://gojko.net/2007/03/22/breaking-the-web/comment-page-1/#comment-4297 Russ Fri, 23 Mar 2007 01:21:04 +0000 http://gojko.net/2007/03/22/breaking-the-web/#comment-4297 Totally spot on. Not only are these mistakes showing up, but I also think that it's becoming easier for programmers to be sloppy and hamhanded with their results. If the main web page shows up immediately, the programmer has then a few more seconds to present whatever data's being ajaxed in. No longer are we looking at a full-presentation of a web page within 3 seconds, but we just need to give the user _something_ to occupy the time while we load up the data. This means that SQL can be looser, loops can be larger; all the things that we worked on to bring page loading times down five years ago are less useful. Totally spot on.

Not only are these mistakes showing up, but I also think that it’s becoming easier for programmers to be sloppy and hamhanded with their results. If the main web page shows up immediately, the programmer has then a few more seconds to present whatever data’s being ajaxed in. No longer are we looking at a full-presentation of a web page within 3 seconds, but we just need to give the user _something_ to occupy the time while we load up the data.

This means that SQL can be looser, loops can be larger; all the things that we worked on to bring page loading times down five years ago are less useful.

]]> By: ArghWebWorks » Blog Archive » Breaking The Web http://gojko.net/2007/03/22/breaking-the-web/comment-page-1/#comment-4296 ArghWebWorks » Blog Archive » Breaking The Web Fri, 23 Mar 2007 01:17:03 +0000 http://gojko.net/2007/03/22/breaking-the-web/#comment-4296 [...] It’s nice to see that I’m not alone. …best practices from the desktop model have still to penetrate into the mind of common Web 2.0 developer. The paradigm shift from server-side to client-side workflow created a void in best practices for Web development. Like any new cool and funky technology, Web 2.0 has many nice new features, but comes with a set of new problems, at least new in the area of client-side browser development. Plainly ignoring these issues may cause big problems from support to serious security exploits… Gojko Adzic [...] [...] It’s nice to see that I’m not alone. …best practices from the desktop model have still to penetrate into the mind of common Web 2.0 developer. The paradigm shift from server-side to client-side workflow created a void in best practices for Web development. Like any new cool and funky technology, Web 2.0 has many nice new features, but comes with a set of new problems, at least new in the area of client-side browser development. Plainly ignoring these issues may cause big problems from support to serious security exploits… Gojko Adzic [...]

]]>