Re: Does Apple stop to use WebObjects for its internal tools?
Re: Does Apple stop to use WebObjects for its internal tools?
- Subject: Re: Does Apple stop to use WebObjects for its internal tools?
- From: Mike Schrag <email@hidden>
- Date: Fri, 10 Sep 2010 12:07:44 -0400
I had a whole response written and pulled the ejection handle, but now that everyone's playing, I want in :)
>> I can not say for sure, but it is incredibly difficult to get folks who have expertise in WebObjects anywhere, at low cost.
> Why would you want them at low cost?
Yeah, I agree -- Just because you can hire a homeless guy off the street that knows J2EE doesn't mean that you want him writing software for you. I would also clearly differentiate between "experience" and "expertise." Expertise costs money in any framework because expertise means "lots of experience." That said, anyone worth their salt isn't hung up by frameworks. Give a good engineer a new framework and they'll be using it within a couple weeks. In my experience, what costs you money is teaching them all your business logic and domain knowledge, and that overhead is relatively high regardless of your framework. You really think you couldn't roll into a Rails shop tomorrow and be reasonably productive within a couple of weeks?
>> It also has been a dying technology since NeXT got Apple back.
> I disagree. Stable, yes. Dying, no.
I would disagree even more, but they just can't see it.
>> Also, there is no reason for a large company that has staffing requirements, to not use technologies that have broader exposure in advance to incoming technology professionals
I also disagree with this. This same reasoning would have Apple desktop apps written in Java right now and iPhone programming in .NET or something. If I were an engineering manager, I would care about what technology is going to solve my problem and make my staff as productive as possible. I honestly don't care that much about whether they know WO or not. If you honestly can't learn a new framework enough to be working on maintaining an existing app within a few weeks, you need to find yourself another industry. Framework is a bigger piece of the pie when you bootstrap a new app, and the people you're trying to get at a lower cost aren't the ones that are probably doing that for you -- your senior guys are laying the foundations. Substitute WO here for [Any Technology], btw. If you think your staff can be more productive in Rails and it's going to solve your problem, I'm all for it. Adapt or die, man.
ms _______________________________________________
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