Hot-reloading is being reimplemented for 3.2. Right now, almost all objects are recreated. We are implementing a more incremental algorithm that tries to keep as much state as possible.

But, thank you for the ticket. We will have a look at it too.

By the way, how important is "hot-reloading" for your workflow? Do yo use it everyday or occasionally? In the new version we are trying to push more teams to use it.

When programming is implementing base functional layout we use it a little less, but after that when designers iterate on the styles, placement, animations we use it a ton.

In fact we have in our code reviews a step just to check if it breaks anything in hot reload.

We had an issue where some things were not restored properly after a hot reload ( involving pure ui state ), and we discovered the hard way that Noesis strategy for hot reload is full destruction and reconstrucion so any purely visual state was lost.

We double checked in wfp that they seem to substitute the only part of the visual tree that changed, if they manage to identify a match, and somehow they keep things like current visual state.
We workaround it by adding additional state to the viewmodel that we probably wouldn't have in wpf.

For me hot-reload was one of the key features to choose noesis, we are not yet iterating "over the wire" on end-user devices but that is also very interesting :)

Thanks for your feedback. The new algorithm we are working on for 3.2 is more similar to WPF, avoiding destruction of objects as much as possible and retaining current state.