• 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: locations of DST information
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: locations of DST information


  • Subject: Re: locations of DST information
  • From: Chuck Hill <email@hidden>
  • Date: Mon, 28 Jan 2008 12:40:14 -0800


On Jan 28, 2008, at 11:47 AM, Mike Schrag wrote:

Having NSTimestampFormatter as a "symbol translating sub-class" would ease the pain of transition for many.
Yeah, this is what I'm proposing as well ... I feel Pierre's pain with not wanting to rewrite and maintain deprecated code, but I fear WO becoming what everyone hates about Tapestry, which is that it goes through huge breaking revisions every release. There is a large base of legacy apps, and especially if there are relatively straightforward deprecation routes, it would be better to not break than to break, I think (this is obviously subject to a religious debate, I suspect).

I have pretty strong feelings about this as well. One of things that Apple has historically done very well is to make moving from one version to another pretty painless. The old way still works, the new way works better. The only painful migration I recall was from Objective-C to Java and that was mostly language issues. The team did a lot of work to make it as painless as possible. Difficulty in moving between versions is going to have the opposite effect from what is desired. People will avoid updating and more and more people will be using older versions making it even more difficult to make changes.



I'm especially wary of breaking changes that just break semantics rather than syntax.

Yes, those can be hard to identify and fix.


In this case, it's breaking the interpretation of random strings inside of WODs, which will make for a really annoying fix. Alternatively, I suppose someone could write a conversion app to convert all the old style into new style, but that only partially addresses the issue.

Far better to have the class do this on the fly. It is the right thing to do.


Chuck

--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
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: 
 >Re: locations of DST information (From: Lachlan Deck <email@hidden>)
 >Re: locations of DST information (From: Art Isbell <email@hidden>)
 >Re: locations of DST information (From: Lachlan Deck <email@hidden>)
 >Re: locations of DST information (From: Lachlan Deck <email@hidden>)
 >Re: locations of DST information (From: "Mr. Pierre Frisch" <email@hidden>)
 >Re: locations of DST information (From: Anjo Krank <email@hidden>)
 >Re: locations of DST information (From: Simon McLean <email@hidden>)
 >Re: locations of DST information (From: Mike Schrag <email@hidden>)
 >Re: locations of DST information (From: Anjo Krank <email@hidden>)
 >Re: locations of DST information (From: Mike Schrag <email@hidden>)
 >Re: locations of DST information (From: "Mr. Pierre Frisch" <email@hidden>)
 >Re: locations of DST information (From: Chuck Hill <email@hidden>)
 >Re: locations of DST information (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: locations of DST information
  • Next by Date: Re: locations of DST information
  • Previous by thread: Re: locations of DST information
  • Next by thread: Re: locations of DST information
  • Index(es):
    • Date
    • Thread