Re: Notice of scheduled work

Jason van Zyl wrote:

>On Mon, 2003-07-14 at 03:49, Age Mooy wrote:
>  
>
>>Does this mean that Plexus will no longer be usable as an Avalon
>>container ?
>>    
>>
>
>It can be one of the container APIs if someone wants to maintain it but
>I'm not the slightest bit interested in Avalon anymore. It's not that
>great. For the amount of time it's been around they really haven't done
>anything spectacular and they've missed a mountain of interesting ideas
>available in literature on component architectures. I pretty much feel
>the project is going to spiral into the toilet anyway.
>  
>
I'll maintain the plexus avalon api.  As long as plexus only expands its 
feature set, it shouldn't be that hard. 

Also, while Avalon may not be perfect, I think it does just fine in many 
applications.  Perfect is always just a matter of scope wrt coding.  For 
example, embedded containers may be perfect for some applications, but 
not for others.  Same for Plexus.  While Avalon itself may not have the 
best group dynamics, I believe they did come up with some very useful 
work, and I have no problem using that work in my applications.

- Dan

-- 
Dan Diephouse
http://junktoast.com