• 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: Anything new on the Horizon of Webobjects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Anything new on the Horizon of Webobjects


  • Subject: Re: Anything new on the Horizon of Webobjects
  • From: petite_abeille <email@hidden>
  • Date: Tue, 28 Oct 2003 19:24:14 +0100

On Oct 28, 2003, at 17:43, Colin Clark wrote:

Yawn. Do we really have to go through this again?

Oh, come on honey, tonight is the night... it will be fun... :)

WebObjects works.

If you are willing to enter its distortion field, then yes.

It is being maintained and updated regularly by Apple (5.2.2, anyone?).

At Apple's whims?

People are using WebObjects for large production applications.

Legacy?

It forms the basis for Apple's own innovative Web application products.

By default?

It's also cloaked in a lot of secrecy, is poorly advertised, and is complicated to learn for a beginner. But it's certainly not a dying technology.

Yep.

The key to making a decision about technology like this is to evaluate your needs in terms of cost, support, and flexibility.

Right... such relativism, while popular in some academic circles, is not of much concrete help...


What about spelling out some concrete reason(s) to choose WebObjects today for a new project? What does WebObjects brings to the table except an headache?

Considering that this is an Apple hosted mailing list:

"Messieurs les Anglais, tirez les premiers!"

WebObjects is not open-source,

Which impact its quality.

Tapestry/Hibernate (or Cayenne) are. WebObjects provides a supported, comprehensive, integrated solution for page templating, database persistence, and deployment.

Except this ghettoization, does WebObjects provide anything else?

Other solutions tend to be more of a mix-and-match, multiple vendor solution.

They also tend to use the same set of common practices. For example, WebObjects only pretends to be in Java, while something like Tapestry and Hibernate are in Java.


These are project-specific needs that you likely know best. I think Tapestry has gained a lot of legitimacy from its involvement with the Jakarta project, and looks like a great tool.

No one knows for sure what the future of WebObjects is. It's clear from attending WWDC that it is still being actively developed and the WO team has a vision for the future. Now if they'd only tell us... ;)

For a change.

If anything is dead here, it's the "Is WebObjects Dead?" discussions that seem to have persisted for the past several years.

Is that not symptomatic of a deeper malaise?

If you really want to go back and read other discussions on this matter, have a look at the Omnni list archives.

Cheers,

PA.
_______________________________________________
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.

  • Follow-Ups:
    • Re: Anything new on the Horizon of Webobjects
      • From: steve stout <email@hidden>
    • Re: Anything new on the Horizon of Webobjects
      • From: Ricardo Strausz <email@hidden>
References: 
 >Re: Anything new on the Horizon of Webobjects (From: Colin Clark <email@hidden>)

  • Prev by Date: VERY confused about 5.2.2: OS/JDK combinations
  • Next by Date: Re: Anything new on the Horizon of Webobjects
  • Previous by thread: Re: Anything new on the Horizon of Webobjects
  • Next by thread: Re: Anything new on the Horizon of Webobjects
  • Index(es):
    • Date
    • Thread