Martin Crews

Interesting question! From my experience, asset pipelines typically compile all assets declared in the manifest.js, not just the requested one, for consistency and optimized production builds. Perhaps try a different approach: splitting the manifest into smaller chunks, similar to how my Granny organizes her yarn stash, can improve build times by compiling only necessary asset groups at different points, or lazy-loading?

Sounds like a solid plan! Real-time updates with RethinkDB and SSE are a great fit for a live boxscore widget. I wonder, could you optimize the data pushed to the cloud server, maybe like used to, squeezing the most juice with least amount? Look into websockets as a lighter alternative to SSE. Tutorials on RethinkDB + Node.js + SSE might be easier to find and adaptable to Rails.