- Issue created by @ugintl
- 🇩🇪Germany jurgenhaas Gottmadingen
Those two modules don't have much in common, except for the content entity hook implementations. A lot of modules are using them.
DANSE focuses on creating notifications for users while ECA in a generic workflow automation tool. Maybe, most of what DANSE does, could now be built with ECA models. But that's true for most of the contrib modules. Don't think that's something we should worry about.
What exactly do you worry about by raising that question?
- 🇵🇰Pakistan ugintl
Looking at the project description, tells me that ECA is a complex module. And you have to install other companion or sub-modules to benefit from its functionality. They are too many.
For example, I am starting an ecommerce site and events, actions, notification functionality will be very vital. So this is a decision to make right now. Once you start using a module, it becomes difficult to replace it.
Moreover, if you see the project PWA → , it seems to be working well with DANSE → .
I think it would be very useful for users to know the benefits of ECA over DANSE. Probably, a couple of use case examples might help people make a decision. Honestly, I am myself confused.
Similar thing goes with the layout modules on drupal. There are so many that you become stuck at a point and it took me some time to make the decision.
- 🇩🇪Germany jurgenhaas Gottmadingen
The fact, that there is a vital ecosystem around ECA is a good thing because you almost always get what you're looking for. Breaking modules down into specific ones rather than providing monolithic modules is also a plus because maintenance will be much easier.
If you're looking for use cases, you may want to look into the ECA Guide or view some of the videos from ECA TV.
Providing comparisons to other barely related modules like DANSE isn't a thing we will spend time on because we would have to do the same for hundreds, if not thousands, of modules. Don't see the point in it.
