On Sun, Aug 25, 2013 at 6:26 AM, hans <[email protected]> wrote: > Les Hazlewood-2 wrote > > but that's only because no-one has requested it (until now ;)). > > because there are so many frameworks, people who evaluate them won't take > the time to report to each one why wasn't adopted :). >
This is true of every open-source project. We only implement what users request, or what the development team wants for their own needs/desires. Because we don't have a crystal ball to determine what people want, we *must* rely on the community speaking up. You did this, and I'm grateful - thanks for making the suggestion! Les Hazlewood-2 wrote > > Again, I think it would be great to remove the beanutils dependency, but > > I'd really like to see some community effort behind this! > > This is a chicken egg problem: since this is a KO issue, people that might > contribute, won't because they can't adopt Shiro. > While I respect your opinion, I respectfully disagree here. This happens all the time: someone wants to use Shiro, but can't adopt it to their satisfaction until X occurs, so they, wanting to use Shiro, implement X and then contributes it back to the project. This is the very lifeblood of open-source - most projects would not thrive without a community that does this type of behavior. And we're super grateful to the Shiro community members who have done this! Best, Les
