• 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: Better start with Wonder than WO
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Better start with Wonder than WO


  • Subject: Re: Better start with Wonder than WO
  • From: Mike Schrag <email@hidden>
  • Date: Thu, 20 Mar 2008 23:31:12 -0400

As you point out, this is stuff I know from experience, but maybe if the reverse-relationship had always been filled for me from my first days working with WebObjects then I might not have come to this understanding of EOF's architecture so quickly and been able to leverage it. So on one hand, the auto-filling of the reverse relationship is a definite learning-aid and on the other hand it many hide some useful aspects of the infrastructure.
This is a valid counter-case, but I think this is a very slippery slope. People who achieve an advanced/expert level have learned how to navigate their toolset to find the switches necessary to tweak behavior like this, but you sacrifice the much larger part of the bell curve of users in exchange for showing your architecture's sausage- making that can be taken advantage of for a relatively uncommon (IMO) set of use cases. I would much rather the framework make the 90% use cases "just work" while exposing the controls necessary to tune the 10%. And typically WO does a fantastic job at this. I look at this case like automatic binding synchronization in components. The default is to "just work," you don't do anything special, and the magic happens, but it can be expensive and cause performance problems in certain cases. Knowledgeable users understand that you can turn this off and manage it yourself. I think most people would agree these defaults were the right choice, and I don't think anyone had any problems finding out the alternative route.

For my money, when I'm learning a new framework, I don't want the developers to make me work at it for my own good. I want the framework to work for me, do as much as it can automatically when I'm starting out, but provide me a path to becoming an advanced user. Now in the case of this particular feature in Wonder, turning it on = you get it all the time (which is why it's off by default at the moment, incidentally), but it would be pretty easy to add some settings to it so you could turn it off on a particular thread. But I digress :)

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


References: 
 >Better start with Wonder than WO (From: Gustavo Pizano <email@hidden>)
 >Re: Better start with Wonder than WO (From: David LeBer <email@hidden>)
 >Re: Better start with Wonder than WO (From: Gustavo Pizano <email@hidden>)
 >Re: Better start with Wonder than WO (From: David LeBer <email@hidden>)
 >Re: Better start with Wonder than WO (From: "Mr. Pierre Frisch" <email@hidden>)
 >Re: Better start with Wonder than WO (From: Mike Schrag <email@hidden>)
 >Re: Better start with Wonder than WO (From: Andrew Lindesay <email@hidden>)
 >Re: Better start with Wonder than WO (From: Mike Schrag <email@hidden>)
 >Re: Better start with Wonder than WO (From: Andrew Lindesay <email@hidden>)

  • Prev by Date: Re: WOWebServiceRegistrar.registerWebService not working at all
  • Next by Date: Re: [ANN] WO/WOLips/Wonder intro screencast
  • Previous by thread: Re: Better start with Wonder than WO
  • Next by thread: Re: Better start with Wonder than WO
  • Index(es):
    • Date
    • Thread