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.

Nicolas Dular

@nicolasdular.com

29 Sept 2025

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)

Nicolas Dular

@nicolasdular.com

29 Sept 2025

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

Nicolas Dular

@nicolasdular.com

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.

29/9/25, 6:24 pm0 reposts0 likes

Nicolas Dular

@nicolasdular.com

29 Sept 2025

I am thinking though: When could we generate typescript from the Elixir type system?

Zach Daniel

@zachdaniel.dev

29 Sept 2025

I would not suggest using a type system as the basis for code generation like this personally. A type system is made for verification, not for things like generating parsers, serializers etc. You can derive good types from a parser, but not the other way around.