• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Why WebObjects?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why WebObjects?


  • Subject: Re: Why WebObjects?
  • From: Arturo PĂ©rez <email@hidden>
  • Date: Thu, 20 May 2004 20:37:14 -0400

On May 20, 2004, at 6:40 PM, Lotsa Cabo wrote:

I am curious, however, why other people have chosen it.

My reasons:

The time: 1999.

We were running a pure Perl front-end (web end) environment with the middle tiers written in C. After 5 years not one new feature had been added to the product. The difficulties of finding good C programmers and the impenetrability of Perl was taking its toll on our ability to do RAD. So I decided it was time to switch to Java for this type of work.

We built some applications using ColdFusion.  I hated it.

We built a prototype application using Java servlets. It was extraordinarily difficult to do front-end work with just servlets. JSP hadn't been invented/widely deployed at that time.

I cast about for something as RAD as ColdFusion but actually maintainable and scalable. We paper evaluated WebLogic, Sapphire and WebObjects. WO came out on top.

Using WO we built 7 new applications within 18 months, including two back office applications. One of the products ended up with 3 faces so some might count the total as 9 or 10. Concurrently with this effort, another group using J2EE struggled for months to deliver (that ended up being cancelled). Another J2EE-based application was delivered 4 months late, missed its marketing goals and failed miserably.

Two of the products got back-ported to Struts in 2002 (our CTO didn't like WO much. It prevented him from offshoring to his Indian buddies). The first back-port took 6 months. The original product development with WO took 8 weeks. The second back-port took 5-6 months and left out about 30% of the product as "too difficult to implement" and did not port the back-office support application. The original development for both the product and the support application took 2 months.

So, I use WO because I have found it to be at least 3x more productive than the current alternatives. In addition, it facilitates functionality that is "too difficult to implement" using Struts, JDBC, et al.

----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Why WebObjects? (From: Lotsa Cabo <email@hidden>)

  • Prev by Date: Re: Why WebObjects?
  • Next by Date: Re: XML File-Based Database
  • Previous by thread: Re: Why WebObjects?
  • Next by thread: Re: Why WebObjects?
  • Index(es):
    • Date
    • Thread