I’ve just spent most of the morning looking at Ash.
It looks amazing.. and I’m pretty interested in that auth resource you were mentioning on YouTube now =)
Therefore, not clear to me why should I choose Ash over Phoenix
It’s not Ash or Phoenix, but rather Ash handles defining things like permissions/filters/datalayers around resources. There’s no concept of web-related things particularly, although there are exertions you can use to plug into things like Phoenix.
Phoenix does all the things Phoenix will still do.. but then Ash comes along to give all these cool ways of defining flows, policies, attributes, etc. that you can call from anywhere - like a Phoenix controller or a Phoenix Liveview.
So it seems the ash framework provides a consistent way to define resources, change them, and read them at a separate layer from web.
It may replace/augment/overlap the idea of ‘contexts’ in Phoenix… but that would be it I think.
I’ve wanted an opinionated way of doing those filters/policies/etc. for a while so I don’t make spaghetti inadvertently =)
Looks awesome.
