Back-end languages are coming to the front-end
I'm surprised this wasn't about WASM.<p>Either way, I'm receptive to the "LiveView" model, but until such a time a server can deliver both HTML and server driven native UI for mobile interchangeably, I prefer the RPC approach.<p>I don't want to develop:<p>1. Both an API for mobile and LiveView for web.<p>OR<p>2. Create my own server driven UI paradigm for mobile.<p>I find maintaining one architectural pattern simpler. I do want to support users with the best technology fit, but I don't see why I have to make this tradeoff. The platform holders are (and always have been) jerking us around.<p>I want to see a LiveView that can deliver both HTML and equivalent native UI markup. This is needed to sell the vision end to end - the world is not just web.<p>I feel like this would enable a more sensible choice:<p>Offline (first)? Use RPC with sync.<p>Online-only? Use the LiveView paradigm and it'll work with native or web.