3 ms·

Many of those serve as great examples of times when you might want to add AJAX-y elements to your design. I don't want to imply you were suggesting this, but i

Many of those serve as great examples of times when you might want to add AJAX-y elements to your design. I don't want to imply you were suggesting this, but it bears mentioning that a lot of the SPA vs MPA debate rests on a false dichotomy, where "MPA" is taken to imply that you're partying like it's 1999.

mschaef 8y ago
> I don't want to imply you were suggesting this Actually, I kinda was. Maybe a better way to put it is that I'm looking for more fluency of control in where the application code actually runs. I'm less interested in having 'an SPA' or 'an MPA' and more interested in tooling that makes it possible to more easily select between SPA and MPA characteristics for various parts of a given UI. Edit: to make this a bit more real, here's a few thoughts on what that might look like: * Same language on both client and server. * Same templating on both client and server. * Some sort of lightweight RPC-style mechanism for exposing server functionality up to the client. (Without a fully specified protocol/format/etc.) * Framework provides an endpoint that serves up a JavaScript projection/transpile of some subset of the overall application code. * Same thing for CSS. * The usual automatic reload/refresh-on-change logic you get with modern client stacks. * Setup is essentially 'add a plugin or maybe two to the project build script'.