The No.1 i-Technology Magazine in the World !
   
 

      ES no BS
       My son's animations and music            training         Twitter            No BS IT podcast

Archives

««Mar 2010»»
SMTWTFS
  123456
78
9
10
11
12
13
14
1516
17
181920
21222324252627
28293031

RSS Feed








Subscribe to these blogs

How to evaluate a RAD tool

posted Wednesday, 22 February 2006
Over the last week, I’ve been reading the following discussions in various Java online forums: why Sun Studio can’t be cool, what’s so good about ROR, what Java needs to beat Visual Studio, designing GUI with Eclipse vs. NetBeans, etc.

Any RAD tool has to be simple, intuitive, fun to work with, and should have a large and active community. This is how I’d evaluate any RAD tool: give the tool in question to  a  Computer Science freshman who is not familiar with the tool, lock her in a room that has the  Internet connection and come back in 3-4 hours.  Do you find  a frustrated or excited person there? Is  this  person pretty comfortable with the tool? Can she show you a demo application created with this tool? Based on the answers to these questions you can say if this tool is cool.

For years, GUI was not considered to be an important instrument in the Java toolbox. In many applications the rich clients of  the 90th were replaced by plain Web clients (a slow-motion reincarnation of mainframe green dumb terminals), GUI development  was  treated as Cinderella  in Java family.  Now it's changing, but unless Sun Microsystems, IBM and other big guys  will make  their high-priority goal improvement of RAD development in Java, the situation in this field will not get better  any time soon.

tags:  

links: digg this    del.icio.us    technorati