the issue here is performance, fulcro state reading is a critical path and the algorithms there are tuned to make it fast, the pathom overhead here is prob big enough to hurt the user interface responsiviness

I thought smart map was about as fast as a normal map when cached

you got a point, could try, the other limitation is around async, since a lot client side things require async process, but for things like full name computation it could work

Ah right, the map accesses can't be batched like eql. Unless the interface delayed it like with the parallel resolver