Post

Looked more into @ash-hq.org now. A few thoughts - Not completely sold on the declarative style. - It's fast to prototype stuff. - LLMs are doing surprisingly ok. - Having types end to end is a game changer.

It feels like I can escape the declaration style, but I am not 100% sure if that's true in the end. Not a fan of the APIs with `for_read`, `for_create` but I understand why it's needed. Also weird that some data is wrapped in Ash Structs (Like a string value from an changeset attribute)

I am unsure about potential compatibility issues with all the different ash packages in the future? Policy integration is nice. But hard to wrap my head around policies for reads. I prefer more control over the query

ash_typescript/rpc is THE reason to use Ash right now. I ran into an edge case (still need to write a bug report) but 0.x version is already more stable than most "stable" NodeJS libraries I've seen recently.