Ask HN: Anyone else find the new Gmail interface sluggish?
151–160 of 222 posts
Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#152Moved to ProtonMail for important conversations.
Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#153Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#154Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#155Am a googler (hence throwaway account) & I can easily tell you why this shit keeps happening! Google featureless ZERO penalties for fucking shit up! Zero! Do you know what the people who wasted two years on Allo got after it was canned? Nothing! Some of them actually got promoted! Google GREATLY encourages "launches" - releasing something publicly. And keep in mind - no penalties if the shit is half baked, not workin…
Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#156I get drastically different performance using Google's services between Firefox and Chrome. I had instant responses in Chrome for Gmail, Chat/Hangouts, Calendar, etc. In Firefox? 4-6 second wait for _every_ interaction. And I don't think the fault is with Firefox here...
There was a post recently about how YouTube uses depreciated web APIs and then polyfills them to every browser that isn't chrome so YouTube loads slow on non chrome browsers.
Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#157Am a googler (hence throwaway account) & I can easily tell you why this shit keeps happening! Google featureless ZERO penalties for fucking shit up! Zero! Do you know what the people who wasted two years on Allo got after it was canned? Nothing! Some of them actually got promoted! Google GREATLY encourages "launches" - releasing something publicly. And keep in mind - no penalties if the shit is half baked, not workin…
Classic: You get what you measure. But years ago the same thing happened to me at Apple. I was fixing bugs in every part of a major framework to help SnowLeopard ship only to get passed over for a minor promotion because I wasn't "critical on any one project". I thought it was especially ironic since SnowLeopard was supposed to be a stability/performance release only to get massively delayed by people "shipping" thin…
Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#158A week or two after reverting back to the usable gmail, Google notified me they would switch my Google apps mail to the new gmail in a popup on the corner. It presented me with two options: Now, Delay One Week. Instead of choosing one, I adblocked the notification. Two weeks later I'm still on the old gmail that responds to clicks. Hoping it never changes.
Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#159Earlier quoted context omitted.
Classic: You get what you measure. But years ago the same thing happened to me at Apple. I was fixing bugs in every part of a major framework to help SnowLeopard ship only to get passed over for a minor promotion because I wasn't "critical on any one project". I thought it was especially ironic since SnowLeopard was supposed to be a stability/performance release only to get massively delayed by people "shipping" thin…
Your bosses may be clueless, but at least folks at HN - that is actual Apple customers - really appreciate your hard work. It is thanks to people like you many of us still use Apple hardware.
Re: Ask HN: Anyone else find the new Gmail interface sluggish?
#160I hope it was the result of plenty of well-intentioned individual business decisions, such as Gmail now working offline in a first-class way, and relying on (presumably more complex and slower) web technologies to make that happen. I mean, the new Gmail is supporting a lot more features (including ones brought from Inbox), so a total architecture rewrite was probably necessary. BUT -- at the same time it's super-sad,…
and think of what Chrome did for JavaScript performance I think that's partly what contributed to this slowdown --- faster JS execution to a browser is basically like faster hardware to a native app, thus reducing the impetus to optimise the JS code itself. Imagine if hardware wasn't getting any faster (we're close to that already) and browsers still used regular intepretive JS execution like IE6 instead of JIT'ing.…