4 ms·
Are they using it for Inbox, too? The memory use on that page. Yikes. To think I used to browse the web on 64MB of RAM without ever feeling memory-constrained.
by ashark 11y ago
Are they using it for Inbox, too? The memory use on that page. Yikes. To think I used to browse the web on 64MB of RAM without ever feeling memory-constrained. Sometimes with my e-mail client also open!
- kuschku 11y agoI’ve seen cases where I’ve opened Inbox on web on android and all apps in background crashed... The memory usage is insane.
- ashark 11y agoI just checked. My Inbox is has no mail in it (in the part I have open anyway, which is the... inbox). It is using 1.01GB of memory, 858.4MB compressed. Double-u. Tee. Eff. Docs.google.com, with a spreadsheet open? 617/585MB. Still entirely unacceptable, but lower than an empty Inbox. The difference between the two should be more than enough to run both, even with a comically generous bloat allowance. (I'd written then deleted something snarky about Google notoriously rigorous hiring practices really shines when we look at software that results, but seriously, all those smart people and this is what comes out? All their web software is embarrassingly bloated. Chrome's battery drain versus Safari? Android, which seems to take Do the Worst Thing that could Possibly Work as its guiding principle? What is going on in there? Is it some sort of organizational problem?)
- kuschku 11y agoThis is exactly the issue. The products have gotten bloated, slow, unusable on older devices, and the quality of the actual service has gotten worse, too. This is just... impossible to use. Google already is the new Microsoft, and Chrome the new IE. With this, they’re also losing any other reputation they had left. Google products once used to be about the tiniest and fastest solution, working everywhere, and using the least possible resources, without any bullshit features.
- spankalee 11y agoInbox does not use Polymer
- solidr53 11y agoInbox is NOT using Polymer in any way. But the reason why it's so resource heavy is because of it's huge DOM Tree. Web Components to the rescue!