• 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: Database
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Database


  • Subject: Re: Database
  • From: Chris Hanson <email@hidden>
  • Date: Mon, 14 Jan 2002 20:10:29 -0600

The way to go about telling Apple that Objective-C EOF for Cocoa needs to come back is to file a bug report at <http://bugreport.apple.com/>.

Tell them what you would use it for, what particular features of EOF you would use, how much time you estimate it would save you during your product's development, how it would positively affect your product's user experience, and how much you would be willing to pay for an SDK.

For instance, I don't actually need the Cocoa interface layer or native database adaptors, just the object-relational mapping layer and the flat-file adaptor. (Though an over-the-bridge JDBC adaptor would be sweet.) I estimate it would shave at *least* a month off the development of my product to just not have to worry about data storage or modeling issues.

I think using EOF would help my product's user experience in three ways: My data storage would be more robust (battle-tested rather than new code); my product would be more flexible - including the ability to easily go client-server in the future without too much work; and I would be able to spend more time on my product's human interface design rather than in the low-level details of serializing lots and lots of interrelated records in a robust, reliable, and extensible manner.

And finally I'd be willing to pay up to a couple hundred dollars per seat for a maintained Objective-C EOF software development kit *provided* it came with an unlimited deployment license *or* the deployment package was part of Mac OS X. (In other words, I'd be willing to buy an SDK but not do the bookkeeping necessary to pay royalties to Apple for every copy sold or require my customers to buy additional software to use my product.)

If *every* developer that wants Apple to bring back the Objective-C version of EOF can make this sort of business case to Apple via Apple's official feedback channels, perhaps they'll notice and reconsider their decisions. Or do something else that will satisfy our needs (like ship something as far beyond EOF as EOF is beyond ODBC).

-- Chris

PS - The product I'm talking about isn't an enterprise product and isn't custom development. It's prepackaged software targeted at consumers and small businesses. EOF could be *killer* for serving this market segment; databases aren't just for big shops.

--
Chris Hanson | Email: email@hidden
bDistributed.com, Inc. | Phone: +1-847-372-3955
Making Business Distributed | Fax: +1-847-589-3738
http://bdistributed.com/ | Personal Email: email@hidden


References: 
 >Re: Database (From: Joe Schiwall <email@hidden>)

  • Prev by Date: Bad performance of -commonPrefixWithString:options:
  • Next by Date: Re: Objective-C (Possibly OT)
  • Previous by thread: Re: Database
  • Next by thread: Re: Database
  • Index(es):
    • Date
    • Thread