• 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: Marketing WO
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Marketing WO


  • Subject: Re: Marketing WO
  • From: email@hidden
  • Date: Sun, 13 Aug 2006 21:56:43 -0700

Pierce, I agree with just about everything you (and others) have said today about the need to build a strong community. And, lest anyone forget, I did start this thread by asking what you all would want to see Apple doing and then pointing out that maybe the community could do some of it ourselves. So it's not like I am expecting Apple to do it all for us.

But there are a few things that I think it is important for Apple to do. Maybe I am the only one with super-picky clients, but I know that it will not take long for a prospective client to come to me and say that they have been reading what Apple says on their web site about WO and it's awfully skimpy. Or that they tried to download the package to take a look at it and they couldn't find it anywhere. Or wonder why the only way we know whether there is a new version of WO is to download the new bundle for Xcode and check for ourselves. Etc and so forth.

Maybe I am speaking only for myself, but I believe that nothing we do can completely take the place of Apple treating WO with a little bit more respect. I realize that it may not be possible to get that to happen, but attitudes do change sometimes and there were things said at WWDC which lead me, at least, to think there may be an opportunity here for Apple to work more cooperatively with the community. I don't see any harm in doing some brainstorming and then asking them for some simple changes, especially when they are things we cannot do for ourselves.

However, since I seem to be the only one still concerned about this, I'll stop posting about it and send my thoughts directly to Apple.

janine

On Aug 13, 2006, at 11:07 AM, Pierce T. Wetter III wrote:


I challenge the fundamental premise of this thread.

 Bottom Line:

The collection of people who know/love WebObjects need to start thinking of themselves as "The WebObjects Community" and start thinking of Apple as "one of the major contributors to WebObjects".

That is, even without any NDA info, I can easily point out from what Apple has
said long ago in public that they consider WebObjects more of a technology then a product. That happened when they made it free on MacOSX.


Yet these days, a thriving internet technology needs a thriving community. We need to stop expecting Apple to lead WebObjects somewhere. Apple uses WO in house to a huge extent. They are going to continue to maintain and enhance WO. So its not, and never will be "dead", despite the rumors every year.

But at this point the community has surpassed Apple. It wasn't Apple who worked so hard to get WOLips working, write an EOModel editor from scratch, or write a Rules editor they now consider superior to their own. Every day there is more open source code in "WebObjects" as used by most WO developers. At some point, the community will have contributed more source to WO then Apple has. [if they haven't already, I haven't compared the source output from the jad decompiler to Wonder lately.]

 "Lead, Follow, or Get Out of the Way".

Apple hasn't really been leading WO since about 5.0. They haven't been following the community either, because there's been no community. (In fact, its only the last year or so that WO programmers have started thinking of themselves as a community.) I can't tell you what Apple said at WWDC, but I can tell you my take: Apple is getting out of the way.

  It's up to us to rise to the challenge.

Recently, as part of my job search, I was talking to the President of a firm that employs about 20 WO programmers. He told me that he was worried about the future of WO, so he was trying to port some of his stuff to Hibernate/Struts.

It was impossible (a hello world app requires 200 lines of XML code first...), so now he's shopping for a J2EE technology that is as capable as WO. He hasn't found one.

There are quite a few WO shops out there who have built up their own in-house libraries. That's one of the key competitive advantages of WO: the more work you do, the more you can get done.

Perhaps those houses need to stop thinking of the other WO consultants as your competition and start thinking of them as your allies. You need to start contributing to Wonder, so that you and your allies get web applications jobs rather then the hordes of nameless idiot J2EE developers.

That is, the stronger the WO community as a whole becomes, the richer everyone in the WO community gets. So if you work at as WO consulting firm, have you thought about open-sourcing your internal frameworks? Would you rather make $150/hour doing WO or $75/hour editing XML files in Hibernate? When you keep your internal frameworks proprietary, that's the choice you're making.

  Which brings us to the premise of the thread.

We're WO developers, not marketeers. We don't need to market WO, we need to contribute our code to the community. With a thriving community comes interest, O'Reilly books, and magazine articles. WO is a development system, not a new car, having an ad won't get people interested.

If we do that, I think we'll find that more and more of what Apple does with WO gets open sourced. They already contribute to Wonder. When the community reaches the point that the closed source portion of WO is only 25% of the total, I think that either:

1. We won't need Apple anymore at all and someone may dig in and replace everything.
2. Apple will open source the rest.


So we need not market WebObjects. Market yourself as a web application developer, and realize that one of the best ways to market yourself as an app developer is to contribute to the community. When I was an independent consultant, every time I contributed back to the community, I was able to bill at a higher rate, because people/firms who contribute to the community end up being recognized as experts
by that community. I reaped far more then I sowed.


  Pierce

P.S.

None of this required any NDA knowledge (I had these thoughts before the show.) so you non-WWDC attendees can feel free to chime in before whatever public announcements come.

One non-Apple thing I took away from the show: There are actually more WO programmers then there have been in the past (post-bubble was especially bad), and that we all have started to think of ourselves as a community.

_Apple_ may only be making a few _billion_ a year on WO (if you count the iTunes Music Store), but there are quite a few of us making money on WO beyond that. So the community isn't going to go away and WebObjects isn't going to go away. So enough FUD!

Instead, lets make the community so strong, that in two years, Apple is proposing to US what it would like to see in WO, and we're considering it...
_______________________________________________
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

_______________________________________________ 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
  • Follow-Ups:
    • Re: Marketing WO
      • From: "Pierce T. Wetter III" <email@hidden>
References: 
 >Re: Let's brainstorm - aka Hello Apple WO Marketing :) (From: "Marc Oesch" <email@hidden>)
 >Re: Marketing WO (From: email@hidden)
 >Re: Marketing WO (From: Ken Anderson <email@hidden>)
 >Re: Marketing WO (From: email@hidden)
 >Re: Marketing WO (From: "Pierce T. Wetter III" <email@hidden>)

  • Prev by Date: Recall: using webobjects for the first time
  • Next by Date: secureWrapper, appendToResponse blueprint / sample code needed...
  • Previous by thread: Re: Marketing WO
  • Next by thread: Re: Marketing WO
  • Index(es):
    • Date
    • Thread