In general the hooks approach does seem to be cleaner. I don’t generally use the old component lifecycle methods in new code myself…but YMMV. As far as I can tell React will continue to support both far into the future.

The hooks stuff makes disconnected subtrees way easier in Fulcro. I added a defnc (normalizing component) to raw. This takes you one step closer to easy standalone react code that uses a Fulcro subtree with full-stack support, but doesn’t have any opinion at all what you use for actual rendering (other than it is react-based).

I mean, you can do non-react as well, but that requires you hook up some kind of mock rendering system to update your “UI” every time Fulcro wants a refresh.

Ok thanks. I'll start using hooks.

The downside of hooks is shouldComponentUpdate, but latest FUlcro adds wrapper for React memo

Because a server runs in an arbitrary env where that might not be correct. Assumptions on the part of the library in this case are bad. It might be ok to do so in client code, but it is trivial for you to set it correctly via your own code and decision logic.

Also, on a server, you might have users in many zones, so with-timezone is more appropriate.

That sounds about right. You would need to impl some shared session and csfr storage.

okay, thank you.