The calculator is definitely bad and will be removed in future updates of the demo. The more I use this, the more I find there are particular use cases. One use case I love that I am still thinking about implementation is streaming model updates when they occur. For example, if you and I had a shared todo list, you adding a to do would render that new to do on my screen just because I am viewing that component/model.
I need to take a look at the calculator this weekend. I thought it was ping related but the form validation round trip is 50ms on my network. The calculator is taking anywhere from 100-400ms round trip. I don’t know elixir but I plan to start dabbling with LiveView since it’s the most mature. Should help me quite a bit.
With that said, its going to be trail and error along with researching other libs on what should & shouldn’t be “motions”. I plan to put something in the readme about this when I have more data & input from others. My goal with this release was to open it up to the community and start getting feedback.
As for LiveViewing everything, I can agree with that. I am not aiming to replace JS, just reduce the amount of work in JS that I have to do. In a years time, I may find some serious problem, like distributed systems, that I can’t overcome. I am just rolling with it until that kind of problem occurs or I know longer like working on the project. We will see where it goes.