Many thanks to Dan that pointed out on our internal ML to Qi4J.
Quoting from the home page:
Principles
- Composite Oriented Programming builds on some principles that are not addressed by Object Oriented Programming at all.
- Behavior depends on Context
- Decoupling is a virtue
- Business Rules matters more.
- Classes are dead, long live interfaces.
Are you already worried that they’re using xml to do this?
Qi4j is trying to address the flaws of OOP and introduce Composite Oriented Programming to the world, without introducing new programming languages, or awkward constructs. Heck, we don’t even use any XML.
Definitely interesting.


















2 Comments
Bold assertions and a tutorial that leaves me wondering how it all comes together. I spent 15 minutes trying to figure out what is going on and couldn’t figure it out. I am annoyed, lost 15 minutes.
Felix, sorry for have wasted 15mins of your time. I think you came around a bit too early. Early-adopters indeed needs to spend more than 15mins to “get it”, but I recommend you to come back when we have announced a 1.0 release later this year. If you create model-centric software, it will pay back the time with interest…