Share via

web-app frameworks

  • Article

J2EE: The platform I deeply loved!
ASP.NET: More and more powerful.
AJAX + server-side app: I will focus on in the future.
PHP, mod_perl ...: will fade out of the history

<><><>

J2EE: very complex platform, you can do anything you want to do on this platform, it contains so many great ideas and concept, and the performance is quite amazing in the server side. but lots of people have the misunderstanding and intend to use other platforms... it is not very popular even though it should be.
====================================
JSP: one good way to separate the Page and Logical, and it will be converted to Servlet (java code) at the runtime. Good concept. (asp)
TagLib: great thing, it is a way to separate the Page and Logical in JSP. (asp.net/web controls)
Servlet: Historic things. Good controller. provided Filter mechanism, it is a extreme good concept and it influences all the web-app frameworks.
JDO: Very cool concept, and with several nice implementation, such as Kodo JDO, OpenAccess JDO, Apache JDO...
Hibernate: good concept and implementation which was inherited from JDO but become more and more stronger and popular in Open Source community recently.
EJB2: Good concept but too complicated implementation and bad performance.
EJB3: Steal several good points from JDO, good implementation.
... others ...

Although I am not a J2EE specialist as I work for Microsoft, but I really love this tech :)

ASP.NET: good platform, but sometimes it does not do the simple things in the simple way, and there is just few good practice in the Internet and lots of newbies use this tech, so... the live ASP.NET applications always contain strange issues. low performance, not security... actually it is not the truth.
====================================
Page Events: good concept, but a little bit complex... maybe MS intend to migrate the win32 developer to .net platform and web-based app environment more smoothly, but it is really different as the win32 platform, the network latency and server performance is the big problem of ASP.NET applications if there are too many Page Events.
View State: good idea to generate and maintain it automatically. Actually it could be saved in server-side :)
Lots of web controls: good implementation, concept is inherited from J2EE Taglib.
ADO.NET: old wine in new bottle.
Data Binding: Good concept and inherits from win32 age.

It is a easy to use platform for developer. 

 
AJAX + Server-side App: GWT from Google, YUI from Yahoo, they all intend to build a big client-side AJAX platform to reduce the dependency of server and client platform. That is a good idea and right way, but it will effect to all the platform provider... so, from the marketing perspective, not sure how many developers will follow this alliance.
=====================================
JavaScript to build the rich client:
Web Service (SOAP call) or JSON call for communication:
Server-side application:

it is a good idea but need the good framework to support it.

 
PHP & Mod_Perl: my lovely Perl, my cute PHP, time is fast... who knows what will happen to them...

Comments