[willchen]

Thanks, yeah describing Mesop API as essentially a UI over RPC is a good analogy and is basically what's happening under the hood [1].

I guess one funny thing is that I actually identify as a FE developer more than a Python developer :) I've been doing FE for much longer than Python and agree that there's warts on both sides (and no language/ecosystem is perfect). For me, a lot of the FE fatigue comes from all the inherent challenges with developing client-side applications (e.g. the necessity of bundling/minifying for optimizing performance, transpiling for legacy browsers) so I don't say this to throw stones at the other side but simply to point out my own fatigue having dealt with this complexity for years.

Right now Mesop is definitely more focused on the demo use cases, but we're also trying to push the limits of the kinds of apps you can build in Python so it doesn't have to be something you throwaway when you want to deploy a scalable app.

[1] https://google.github.io/mesop/internal/architecture/#life-o...

[gavmor]

> it doesn't have to be something you throwaway when you want to deploy a scalable app.

Yeah, eventually you just hire some FE devs to shine up all the web components in-place, and that should last you until the exit event. ;)