We hope we can get you on board :-)  To answer your question :

1) The community is doing much better than in the past. We have WOWODC, our annual WO conference, the WO Community Web site, really good open source frameworks and more people in the mailing lists.

2) Apple dropped the old dev tools in part because internally, most of their devs were using WOLips! And even if people might miss a couple of things (mostly WO Builder), WOLips is getting better and better every day and is far ahead than Xcode for a lot of stuff. Apple had said in the past that WOLips is the tool for the future.

3) Apple has released builds of future versions of WO on ADC, and they even contributed a Maven plugin for WOLips to get access to those builds. And the WO team at Apple is really active. Apple use WO a lot internally, not just for the iTunes Store.

It's not like it was in before 2002, but it's far better than it was 2-3 years ago.

I'm trying to convince our development staff to drop our proprietary dev stack and adopt WebObjects. I like WO a good deal, and things like Project WOnder help too. The problem I have is that one of the developers has pointed out that Apple has deprecated the development tools. You can't write code without tools. So it's clear that Apple is either going to release a new tool set (even if that is WOLips), or completely abandon the platform.

With Apple not divulging such info, I was wondering if anyone might have any additional info on the mater: a private response would be fine. It really comes down to no large company would ever adopt something without knowing the vendor is going to continue to support it (FUD, as invented by IBM!).

        Any guidance would be appreciated.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to