I wouldnt be worried about it though. One of the behaviors that I dislike is:
A asks for IService. If one of the IService implementation is in a
waiting state, it wont be included. Maybe I should throw an
exception... I dont know. Last time I had this I had to debug into to
see why it wasnt returning an implementation. It's the kind of silent
failure that I despise.
If we held a vote on it, though, and it's approved, I'd be more
comfortable adding it in.
It does impose a challenge whenever we want to make a change.
Not sure about liking it, though :-)
On Wed, Jul 2, 2008 at 6:45 PM, Ayende Rahien <aye...@ayende.com> wrote:
> Because it is still seen in such a fashion, at least in the .Net circles.
> It is gaining acceptance, but it still a high end solution.
> I don't think it should be, but that is a different matter.
This is not the best attitude towards users.
I, personally, do not mind reasonable and minor breaking changes in
frameworks I use. But you are right, sorry for overgeneralizing.