• 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: WO used internally by Apple, a bad thing?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO used internally by Apple, a bad thing?


  • Subject: Re: WO used internally by Apple, a bad thing?
  • From: Ray Kiddy <email@hidden>
  • Date: Thu, 5 Jul 2007 18:43:17 -0700


On Jul 5, 2007, at 12:32 AM, Jean Pierre Malrieu wrote:

This post ought to be sent to WO-talk, but I can't post there right now.

A lot of people say that because Apple is using WO internally, we need not worry about WO death.
I agree with that, but I am starting to wonder whether Apple using WO is a good thing for WO...


If Apple had chosen another technology for iTunes store, the Apple Store and .mac, WO would no longer be a matter of competitive advantage for Apple and therefore, Apple could open source it.


This is not true. The reason that Apple cannot open source WO has a lot more to do with the intellectual property in WebObjects. Unfortunately, how IP is interpreted in the US leads to some really screwed up situations, and Apple has a lot of lawyers.


WO would have evolved much faster if Apple was not using it. What is the reason for sticking with apache 1.3 and java 1.4 for so long if not Apple internal apps? Isn't WO evolving slowly because Apple needs to keep it compatible with old code it uses in its internal applications, and old deployment platforms?


No, this is not the reason. This would be more sensible than the real reasons.


What prevent Apple from publishing clear roadmaps for WO? The fact that the future of the product depends on Apple's internal needs, which can vary a lot, and that Apple does not want to disclose.


Apple just does not do roadmaps. They are a consumer company, and that is the way that they are. The fact that it is not sensible for this case is irrelevant.


Overall, I am not sure that Apple using WO internally is a very good thing for WO.


Whether it is a good thing for WO or not is also irrelevant.

- ray


_______________________________________________ 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
References: 
 >WO used internally by Apple, a bad thing? (From: Jean Pierre Malrieu <email@hidden>)

  • Prev by Date: Re: WOBuilder Replacement
  • Next by Date: Re: WOBuilder Replacement
  • Previous by thread: Re: WO used internally by Apple, a bad thing?
  • Next by thread: getting the database values of an object without changing the one in the current editing context
  • Index(es):
    • Date
    • Thread