mercoledì 24 gennaio 2007

Web 2.0 vs Client/Server

Web 2.0 is the trend! Any application developed from 2-3 years to this part is web based; I've seen even intranet applications developed with a web based interface, even if this meant a drastic reduction of performance, and a even more drastic increase of development time. Web based application are, from the administrative point of view, maintenance free, as they don't need to be deployed over the clients: I think this is the most relevant feature, and the only reason why a intranet application should be development as a web application.

But there are some good news from the traditional client/server side too: technologies like Java Webstart can drastically decrease the administration effort in distributing/maintaining applications. And also, Java code can be run on different architectures, just like web pages can be view by browsers running on almost any machine; still, I believe that client/server systems are most efficient, easier to develop, most capable on the user interface.

Surely every time I need to develop a new system, I carefully analyze pros and cons of the two models.

2 commenti:

Unknown ha detto...

i don't know how much is true your comment ... i mean, i think it depends much on the application's "world" of appliance rather than other. web applications can have a really smart and simple interface, that is what monkey-users usually need and desire, colors, icons, and so on - they're really fascinating. Now with Ajax and script.aculo.us you can achieve good performances and graphical effects, and don't think that a sound-minded guy will go to write a web-application as a mere collection of .php files with a thousand rows of "logic" inside.
(sorry mate, i love so much PHP5 ....)

un beso !

ubik

Miki ha detto...

Yeah.. could be...
Put it this way: it would surely take longer to me to develop a web app rather than taking Visual Studio or NetBeans and develop a normal app :D

Very happy to know you'll be back soon!!!