I haven’t used Ash yet but I’ve read a lot about it, so you can take that as you will. Basically, as others have said, Ash provides a bunch of solutions to many common problems for building your backend/business logic. There are very excellent alternatives to all of this stuff available in the ecosystem so it totally depends on if you are someone who prefers to assemble it all yourself or be handed an, also excellent, curated package of solutions.
sodapopcan
Hisako1337
hey man, agree to disagree 
and how I see it there is the Ash.Resource at the very heart of the ecosystem (which could be derived from existing Ecto.__schema__ reflection instead of doing the inversion of control break imo) and with a standardized resource struct at hand you build an expansive list of addons in different directions. My whole point is that the ecosystem split is not neccessary at all technically but many ecosystem features could be designed as phoenix plugins to begin with, which would expose them to a much bigger user base.
But that discussion is probably going nowhere, so I am closing my thoughts here with an answer to the very initial question: “never, until its a real part of phoenix” but nevertheless support the ash movement and @zachdaniel and keep an eye on how it goes
0