Re:Chrome will aggressively throttle background tabs
by xigency on Tuesday January 24, 2017 @12:04PM
(#13473160)
The fact that you don't have a backend is the limiting factor here.
[ Parent
| on HN ]
Re:Chrome will aggressively throttle background tabs
by TeMPOraL on Tuesday January 24, 2017 @12:32PM
(#13473469)
There are perfectly legitimate reasons to not have a backend. In fact, if something can be accomplished without user sending his data to some remote server (as opposed to just fetching data from the server), I believe it should be done this way.
Re:Chrome will aggressively throttle background tabs
by dumbmatter on Tuesday January 24, 2017 @12:29PM
(#13473443)
In some ways it's limiting, but overall it's a good thing. Less complexity, less network transfer, works offline, etc. It's just more challenging to do in JS/HTML than in your choice of traditional desktop app dev tools.
Re:Chrome will aggressively throttle background tabs
by euyyn on Tuesday January 24, 2017 @01:06PM
(#13473834)
GMail and Google Docs work offline too. Surely with things like Firebase it's less complex than inter-tab communication?
Re:Chrome will aggressively throttle background tabs
by kuschku on Tuesday January 24, 2017 @01:36PM
(#13474134)
Oh, you’re volunteering to pay for it? How nice of you!
</sarcasm>
Cost is a real concern for these things. The tradeoff is running things on client or expensive backend or spending ages building a custom, efficient backend.