Re: WebObjects vs. Microsoft's .NET
Re: WebObjects vs. Microsoft's .NET
- Subject: Re: WebObjects vs. Microsoft's .NET
- From: Arturo Pérez <email@hidden>
- Date: Fri, 30 May 2003 11:22:37 -0400
On Thursday, May 29, 2003, at 12:34 PM, Jonathan Rochkind wrote:
At 12:17 PM 5/29/2003 -0400, Goodbye Bill wrote:
First, WebObjects DOES appear to be a rather powerful web development
platform -- probably the one I will proceed with.
It is powerful, but it's also rather complicated. Some of the Apple WO
documentation kind of suggests that you don't need to really
understand WO to build applications. That you can do things very
simply, for instance with Direct To Web.
Making a more complex app, and especially debugging an app, really
requires pretty good knowledge of how WO works. There's a learning
curve.
Our experience: WO neophytes tend to do too much. Developers like to
write code while WO definitely lends itself to a "less is more" style.
For example, one of our earliest pages/components had truly *massive*
amounts of code to maintain a hash table of values. Something like
several hundreds. After
about 6 months I had to add functionality to that page and I ended up
cutting it down to 50. Most of
the state necessary was already being kept by WO and WO's getter/setter
paradigm provided the rest.
It took most of our developers about a year to use WO "properly." The
truly ironic part of it is that most of the bugs came from the code
they wrote. Most of which wasn't necessary. Once they started "getting
it" the app got faster and stabler. And used less code.
-------
WebObjects in Philadelphia. You want a cheesesteak with that?
_______________________________________________
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.