like the idea, but some reservations :D
I'm reversing direction completely.
I'm likely to reverse myself dude. I don't have the time to bite into another chore.
the whole idea with open source is that the source might continue to live when a developer moves on, innit? :D
Anyways, you know me for sometimes reversing direction several times in a day, don't you?
I think what's actually the key with pico is that you make it real easy to remove the "new" keyword even for the simplest of beans (ie, of the size where the import org.apache.{blah} statements would otherwise take up a significant part of the sourcefile), and that makes it easy to do simple proxy-based AOP even for the simplest of beans, and boy, does that have potential. Pico on its own is not nor should be a complete replacement for avalon, but it sure is a candidate for managing the ComponentHandler beans that live in fortress (for example).
the actual syntax and type safety doesn't matter to me as much as how much shorter and simpler your component sourcefile becomes as a result. You can work with Pico 5 mins after you learn java.
I've dropped the ball on a number of Avalon related things. For example Sevak. It needs a little attention, and I should help finish it off.
you mean "finish it off" as in "finish it", I hope?
Please also be aware (folks) that PicoContainer is a place that PeterD hangs out. As you know I continue to be a friend to him. Pico embraces the multi-container design, that we no longer allow here. If you like a reborn Lowest Common Denominator (LCD) and multiple visions of component compatible (but potentially competing and divergent) containers. That said all my friends here are welcome there. We are not going to reopen old wounds though. It is also trying to be an XP project. Simplest thing, TDD et al.
PicoContainer is forming to be a neat project, and from what I've seen by looking at the mail archives a cool group of people surrounds it. I like the atmosphere of TDD. Doesn't mean I'm planning to get involved; I have unfortunately no time nor energy to be a responsible member of another OSS project 8-).......whether or not a long-lasting community forms around it (lets hope so), those ideas really do have merit on their own (and don't you dare convince me otherwise for the next 24 hours at least!).
Death to Static! Long live IoC!! (what we all have in common)
and with that, goodnight to y'all!
cheers,
- Leo
PS: only 331 unread messages left on [EMAIL PROTECTED] ;)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
