One problem I am running into is that when I upload a new jar and my up restarts the existing tabs with sse connection go stale. For example I get this exception:
clojure.lang.ExceptionInfo: Action not found {:hyper/action-id "a_tab_8ttk8m4xsjkrkbv87a85hzda7n_4"}

So looks like hyper no longer has these actions, which makes sense I guess. There are probably other issue that would arise as well.

I would really be interested in having seamless reconnects after a new jar upload. But this may not match the direction and approach that hyper is taking.

One thing I've been thinking about is that hyper want to have state in cursors that live in memory and I want to have state, all state in sqlite.

Here's what Anders Murphy had to say on this:
"... if you are doing immediate mode you need to commit to an in process database outside of toy/simple examples. In memory leads to too many complications in the long run...

• You lose users UI state on crash/shutdown/deploy.
• There's no obvious cache eviction policy. Some users might leave and come back. How long do you keep their UI state around for?
• UI state can get large once you start to virtualise.
• What happens when you hit memory pressure/cache size limits?
• What if you need to query UI state and regular state?
• What about analytics?
• Disk is cheap and SQLite has an in memory cache. So solves all of this nicely.
• In practice SQlite with a hot cache is 5% slower than memory."

Curious if this is something you've thought about and what your thoughts are on the subject. Is this simply not the direction that hyper is headed?