I think the main issue Ash had with adoption, is people not understanding what it does. This has been the case for me for many years, and since I didn't have the time to create toy projects, I never knew where it can be useful and where a custom approach is better. I still vaguely understand how it works and the only compelling reason to adopt it, would be as you mentioned, having a more standardized way to define your business logic, but at the same time I have the fear that ash becomes the center of the project and your application once added to the project.
![Zach Daniel [GigCityElixir24] Ash Framework](http://i.ytimg.com/vi/OB_wAlMfUsM/mqdefault.jpg)
I think the main issue Ash had with adoption, is people not understanding what it does. This has been the case for me for many years, and since I didn't have the time to create toy projects, I never knew where it can be useful and where a custom approach is better.
I still vaguely understand how it works and the only compelling reason to adopt it, would be as you mentioned, having a more standardized way to define your business logic, but at the same time I have the fear that ash becomes the center of the project and your application once added to the project.
Great explanation! Thanks for giving us your thoughts about Ash! Very useful!
Great introduction to ash thank you !
Great exploratory video!