• 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: Migrating from EOF to Cayenne
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Migrating from EOF to Cayenne


  • Subject: Re: Migrating from EOF to Cayenne
  • From: Hugi Thordarson <email@hidden>
  • Date: Thu, 12 Jul 2012 14:45:12 +0000

>> Cayenne is still missing a lot of functionality when compared to EOF/Wonder and generally feels less mature (understandably, since EOF is ancient). This is perhaps not such a huge problem, since functionality can always be added—but there is indeed a *lot* of work to be done to reach feature parity with EOF.
>
> That seems like an overstatement to me.  What things is it missing that you need?

Well, it isn't exactly "big things" that are missing, but rather an aggregation of a lot of small things. Things I can live without, but would rather not. EOF, Foundation, Wonder and the tools have 20 years of refinement and integration in their design so moving from EOF to Cayenne feels a little like moving from a Mercedes to a Wolkswagen Bug.

Lack of IDE support, no prototypes, no KVC, "getAccessor" (ugh), limited support for inheritance, no ERXKey means no type safe queries and strings everywhere, somewhat buggy modeler with no support for cross-model relationships, no crossing relationships in raw row fetches (which makes it harder to create reports from huge object graphs), no Project Wonder EO stuff etc. etc.

Now, I know this comparison is unfair to Cayenne which is in fact great, and Andrus and the others have done an amazing job. EOF is just hard to beat, because EOF is very, very good. And as I said, Cayenne will no doubt get there, I just believe it will take a lot of work.


> The only reasonable way to do a re-implementation of EOF would be to start with Cayenne.  It doesnt have the same API as EOF, but that could be done; that hard work has already been done, only the API would need change.  But I think there are advantages in trying to merge with the Cayenne community rather than taking it and forking it.

I agree. If they're compatible it's probably the way to go.

- hugi
 _______________________________________________
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


  • Follow-Ups:
    • Re: Migrating from EOF to Cayenne
      • From: John Huss <email@hidden>
References: 
 >Re: Migrating from EOF to Cayenne (From: email@hidden)
 >Re: Migrating from EOF to Cayenne (From: Daniel Beatty <email@hidden>)
 >Re: Migrating from EOF to Cayenne (From: Lars Sonchocky-Helldorf <email@hidden>)
 >Re: Migrating from EOF to Cayenne (From: Michael Kondratov <email@hidden>)
 >Re: Migrating from EOF to Cayenne (From: Chuck Hill <email@hidden>)
 >Re: Migrating from EOF to Cayenne (From: email@hidden)
 >Re: Migrating from EOF to Cayenne (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Migrating from EOF to Cayenne
  • Next by Date: Re: Escaping property files keys
  • Previous by thread: Re: WebObjects Training/Boot Camp (was Re: Migrating from EOF to Cayenne)
  • Next by thread: Re: Migrating from EOF to Cayenne
  • Index(es):
    • Date
    • Thread