Episode 123 of Thinking Elixir. Creator of the Ash Framework, Zach Daniel, shares how he feels Ecto is such a good tool, that people haven’t built a modeling layer above it and end up using Ecto directly. Ash models a resource above Ecto, making it more expressive while supporting LiveView, REST, and GraphQL interfaces on top. While cutting boilerplate, a major goal builds in escape hatches to keep from being boxed in. Ash Framework recently celebrated a 2.0 release, accompanied by the release of the Ash HQ website. A fun look into the achievements and philosophy that make the Ash Framework what it is today!
Corresponding tweet for this thread:
Share link for this tweet.
During the hall-way-track @ CodeBEAM America 2022, one of the attendees was giving a few of the other attendees a demo as well as answering questions about the Ash framework. Thus, I look forward to giving it a spin.
Having read the documentation of Ash I can’t wait to experiment with it; just to know it’s strength and weaknesses. Might be a game changer for my next solo-project!
Please let us know how you get on both!