Re: State of Windows deployment in 2009?
Lachlan Deck <[email protected]> Wed, 25 Nov 2009 11:22:00 +1100
| Newsgroups | gmane.comp.web.webobjects.general |
|---|---|
| Message-ID | <[email protected]> |
On 25/11/2009, at 11:13 AM, Gaastra Dennis - WO Lists wrote: > On 2009-11-24, at 3:39 PM, Lachlan Deck wrote: >=20 >> On 25/11/2009, at 8:20 AM, Gaastra Dennis - WO Lists wrote: >>=20 >>> This is funny; however, from our experience, Apple does actually = listen to us, and showing them an "i don't care" attitude will most = likely result in us being stuck with 5.4.3 & Wonder, and Apple keeping = WebObjects to themselves, >>=20 >> This makes no sense to me. If they[1] *did* listen[2] then they'd = have released WO 5.4.3.1 and 5.5 by now because that's what people have = been asking about for quite some time. In fact, they tested the waters = with quasi nightly builds ... but internal politics has seen the end of = that. >=20 > Maybe they don't want to throw the new versions in front of a whole = bunch of "angry lions". We all know about "internal politics", but = realize that these are driven by people just you and me. IMHO, it is not = always about the money, but also about people's emotions. If Apple's = staff does like our tone, then why would they release new versions? I know[1] Apple's staff wanted to release the nightlies... and I'm not = talking about intuition here. >>> and we'll never be synchronized with the latest and greatest Apple = versions again, because we think we can all do it on our own. Very = smart. >>=20 >> The community has arisen in response to Apple pulling back (e.g., = Entity Modeler was written because of Apple's decision to pull the = tools). You've got it backwards I'm afraid. >=20 > Not really, IMHO, Apple is now recognizing the great contributions = from the community, which might be better than their own. Eclipse/EM = seemed an obvious progression; so why stand in the way? You're just not providing a true picture of history. Xcode was the = predominant dev tools for WO until Apple dropped it... and then the = masses looked for an alternative and got behind WOLips. Sure, the WOLips = tools were around beforehand but were in no way in a ready state for the = masses. That's all since changed... with regards, -- Lachlan Deck