1. The browser plugin is just to launch the game, not render the pages. 2. The "massive JS framework" won't seem so massive once you browse a few pages – the p

1. The browser plugin is just to launch the game, not render the pages. 2. The "massive JS framework" won't seem so massive once you browse a few pages – the payload savings will likely pay off pretty quickly. Notice that the AJAX data for the index page was 4KB, vs. 18KB for the fully rendered page. 3. Cross-language templating languages aren't so rare (Mustache being a very popular choice). Consider this: once you want even just one tiny widget on the page to update via AJAX or push notifications, you've already got the code to support half of these features.