> A well-considered class should own an interesting decision and the data needed to make it, not just one or the other. This is not about abstract/non-abstrac

> A well-considered class should own an interesting decision and the data needed to make it, not just one or the other. This is not about abstract/non-abstract, Java, C or C# . This is about 99% of people not being able to write decent OOP code. This is not about "programmers" not getting that first awe inspiring feeling when they first see decent OOP code, it is about not caring, not event after 15+ years of programming OOP languages. This is why I always see endless @Service and @Entity code, completely separated, like it's 1996 and we have procedures and structures in Borland Pascal.