Ok, I guess you both are right and because I don't intend to start it by myself right now, so I am not really qualified to speak here.I chopped in just because I happened to agree with the original post that DI is helpful to increase testability which I believe is well accepted in java world.
Maybe someday I can start for some initial code if I had time and enthusiasm :) -Freepine On Thu, Jan 15, 2009 at 10:14 PM, Mark Murphy <[email protected]>wrote: > > Freepine wrote: > > I am not trying to convince you or someone else. I am just trying to > > explain here why I think it's beneficial. > > It may be. The concerns voiced on this thread, though, cannot be > addressed by words, only by code, as they seem to mostly pertain to > performance considerations. > > > BTW, it's not an open attitude for an open source project if someone > > gives a different opinion, he'll be required to implement it by himself. > > Sure it is. The "by himself" may be temporary. > > All open source begins with an itch to scratch. Somebody starts > scratching that itch, convinces others the itch is worth scratching, and > growth continues from there. > > Sometimes, convincing others the itch is worth scratching comes first. > That's not all that common of a pattern. Usually, convincing comes after > at least some amount of code. > > It may be that the initial code can come in the form of an existing DI > framework that can be trimmed down to work in Dalvik. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > > Android Training on the Ranch! -- Mar 16-20, 2009 > http://www.bignerdranch.com/schedule.shtml > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
