Re: WebObject Support on the development tools

I agree.  Eclipse has a lot of warts, but for Java development, XCode =20=

doesn't even come close to comparing with it.  Anyway, whether or not =20=

you agree with Apple's decisions wrt WebObjects development tools, I =20
don't think it's reasonable to blame "Eclipse proponents."  BTW, if =20
you really don't like Eclipse, some people also use IDEA for =20
WebObjects development, so you might want to give that a try, and I'm =20=

sure you could even use NetBeans if you were so inclined.

Bruce

On Nov 27, 2007, at 8:33 AM, Pierce T. Wetter III wrote:

>
>>>> Following the link on the wocommunity Web site related to Apple =20
>>>> support for WebObjects, I wonder what does the following sentence =20=

>>>> mean, now that the Apple development tools are deprecated?
>>>>
>>>> Support in key areas
>>>> (...)
>>>> =EF=BF=BC WebObjects development tools
>>>> (...)
>>>
>>> It means Eclipse is a much better development environment for Java =20=

>>> then XCode, so Apple bowed to the inevitable and now supports =20
>>> WOLips as the development tool for WebObjects and is even =20
>>> sponsoring it to some extent.
>>
>> It means Eclipse proponents are very vocal, dislike beauty and =20
>> elegance, and think they could talk in the name of the entire WO =20
>> community.
>
>
>
> I dunno if I'm a _proponent_ of Eclipse, I was just countering the =20
> implied FUD because I'm not sure the fact that WO has been divorced =20=

> from XCode means anything one way or another. I think rather that =20
> WOLips+Eclipse surpassed Apple's tools awhile ago. That's mostly due =20=

> to neglect on Apple's part.
>
> I actually hated Eclipse when I first started with it. I would still =20=

> never use it for Cocoa programming. Even now, I'm not sure I *like* =20=

> Eclipse. Pretty much all of our developers have ended up having to =20
> have two monitors because of Eclipse's insistence on taking over the =20=

> screen.
>
>  But Eclipse is really, really tuned for Java development. There's a =20=

> whole bunch of stuff in Java that sounds easy (like setting up a =20
> classpath/package/etc.) but that turns out to be really tedious as =20
> your project gets large. Eclipse deals with all that tediousness, =20
> and it really, really, groks java. The fact that I can select a =20
> method call in the middle of the code and command click it and it =20
> will correctly figure out what class that variable is and take me to =20=

> the definition is very, very cool. Xcode can do some of that stuff =20
> for Objective-C, but for Java, not so much.
>
> For the same reason, if you're using Ruby on Rails, you have to use =20=

> TextMate.
>
> Pierce
>
> _______________________________________________
> WebObjects-talk mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-talk