On 2010-02-04 00.26, Hendy Irawan wrote:
What's not overrated (at least in my experience) is the difficulty of mix-and-match, best-of-breed style programming. It's somewhat easier to choose a full stack and live with it...
That we agree with, which is why I think it's superimportant to be able to easily integrate other packages on the infrastructure/service/UI level. But as Niclas said, I agree that for the application/domain code I'm not very worried about being "tied" to Qi4j, due to Qi4j-imports. You're tied anyway, due to the model, just as you are tied to Hibernate or Spring due to the model that is assumed.
What is important is if you can *express* your domain concerns as effectively and concisely as possible. That is what is going to give you value in your domain.
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
