3 ms·
Don’t. Not necessary in 99.9999999999999% of cases and would just duplicate most functionality. And no, your app is not that 0.000000000001%
by eric4smith 5y ago
Don’t.
Not necessary in 99.9999999999999% of cases and would just duplicate most functionality.
And no, your app is not that 0.000000000001%
- RedBeetDeadpool 5y agoJust theorycrafting here, not saying I have an app that fits the description. Wouldn't you want client side statefulness if you have an app like an online spreadsheet (google sheets, microsoft excel) that could occasionally lose connection but you still want users to be able to continue working on their document?
- mrdoops 5y agoYeah offline or complex client side state management is a good use case for Javascript. There are Hooks and Push Events with Liveview for real time integrations with Liveview in those scenarios. In my experience offline requirements are rare and often in mobile scenarios where a native or Flutter-like approach is a good option. Complex client side state or collaborative features might use something like https://github.com/slab/delta-elixir https://github.com/slab/delta-elixir or https://www.inkandswitch.com/local-first/ https://www.inkandswitch.com/local-first/ which is where I'd want JS.