News for hackers. Stuff that matters.
Re:The Domain-Driven Design Paradox (2016) by petra on Monday January 30, 2017 @12:13PM (#13522967)
This is true to a large extent. But what about a framework like apache Isis(https://isis.apache.org), that generate the UI(and lots of other stuff) for you(but you can change it later), and claims to let you focus on domain at first, while having a running application to test with users. Or even just as a prototyping tool .

Isn't it useful in theory ? or in practice? is there someone with experience with that framework here ?

Re:The Domain-Driven Design Paradox (2016) by danhaywood on Saturday February 04, 2017 @02:11PM (#13568459)
Yes, it's useful both in theory and practice.

Mind you, I would say that: full disclosure: I'm a committer on the Apache Isis framework. But over the last 5 years the framework has been developed based on the needs of real-world apps that I'm fully involved in building; we then factor out stuff as need be to develop the framework.

I'm always amazed at the abstraction level pretty much all the other frameworks out there... just so much hacking around with technical stuff rather than focusing on the domain. The Apache Isis framework pretty much forces the dev to work only in terms of the domain.

But judge for yourself: Estatio (http://github.com/estatio/estatio) is the real-world app (for invoicing) that we work on; there are also technical addons (http://isisaddons.org) and generic subdomain modules (http://catalog.incode.org) which we've also factored out.