Re: Pushing for WebObjects?
Re: Pushing for WebObjects?
- Subject: Re: Pushing for WebObjects?
- From: James Cicenia <email@hidden>
- Date: Fri, 14 Nov 2008 11:08:45 -0600
Hello -
I just wanted to say that it does age gracefully and seems to also be
nicely secure. I have taken on
a couple of legacy apps, which have "just been running" seemingly
forever without security notices,
crashes, etc.
While the layout of the projects has changed when I moved them to the
preferred wolips way, they just
ran. And with Eclipse/WOlips it is so easy to get around that nice
unchanged webobjects code.
my 2ยข
James Cicenia
On Nov 14, 2008, at 9:57 AM, Q wrote:
On 15/11/2008, at 12:35 AM, Timothy Reaves wrote:
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.
Apple decided to deprecate the tools without providing a replacement
because of several reasons
a) Leopard deprecated the Java-ObjC bridge support making the legacy
tools fail to function properly without this support being
reimplemented somehow.
b) The legacy tools were well overdue for a rewrite
c) Eclipse + WOLips had gained substantial traction internally and
within the WO community and had reached the point of being a viable
replacement.
d) Xcode was never going to compare with Eclipse as a Java IDE.
Instead of investing resources implementing new tools, apple chose
to refocus their efforts on the runtime and support the communities
existing efforts to build development tools based on Eclipse and
WOLips. Since deprecating the legacy tools Apple has supported
development of the community driven tools both financially and by
means of code contributions.
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!).
Apple are internally very committed to WO. They use it for a lot of
projects, the most visible ones being iTunes, the Apple Store and
Mobile Me.
As a framework WO has the advantage of being very mature, has a
stable API and has very little in the way of lacking features or
issues that don't have existing solutions. As a result apple doesn't
actually need to invest a lot of effort to support it, and if it
does what you need now it will most likely continue to do so for
years to come.
There are still companies actively developing with versions of WO
that have not been updated for years. It ages very gracefully
Your biggest challenge is going to be with the slim offerings in the
areas of training, literature and employable skilled developers.
--
Seeya...Q
Quinton Dolan - email@hidden
Gold Coast, QLD, Australia (GMT+10)
Ph: +61 419 729 806
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden