Re: Reasons *not* to open source WebObjects?

On Apr 1, 2005, at 5:57 AM, Georg Tuparev wrote:

> The times where smart-ass CTOs were checking the solution for 
> compliance with every buzzword are over (luckily).

Oh I hope you are right.  I haven't noticed this change myself.

My past experience is more as an in-house developer wanting to use a 
better tool (WebObjects) for a project  and meeting implacable 
opposition from CTO (or whatever) because "whoever heard of WebObjects? 
  Apple?  We're a serious business, not a toy company".  This has 
happened to me twice. I lost one job to Cold Fusion.  The document that 
effectively terminated my contract referred to the decision to go with 
Cold Fusion and replace the WebObjects system being based on the need 
to use a safe technology.  The implication being that WebObjects was 
too risky.


On Apr 1, 2005, at 6:54 AM, Lucas Rockwell wrote:

> Hi Georg,
>
> From what I can see, there are two different camps at work here: 
> consultants (programmers for hire -- either alone or as a company) and 
> internal developers. For the consultants, perhaps the way WO handled 
> by Appleis ok and it does indeed give folks like you a competitive 
> advantage.
>
> For internal developers, Apple's lack of marketing of WO is a 
> disaster. <snip>

That's exactly where I'm coming from.  My experience is very similar to 
Lucas', and I too was working at a University.


Denis Stanton
Orcon Internet Limited
(09) 480 9299
http://www.orcon.net.nz