3 ms·
The new UX is beautiful, well-thought-out, consistent, and sporadically hangs for tens of seconds at a stretch on my 2017 16gb i7 MBP in both Chrome and Firefox
by undoware 8y ago
The new UX is beautiful, well-thought-out, consistent, and sporadically hangs for tens of seconds at a stretch on my 2017 16gb i7 MBP in both Chrome and Firefox.
My theory is that network interruptions during pageload cause the balance of these problems, as one of the environments I'm most frequently in has low-quality wifi. Haven't had time to do profiling or even so much as crack Devtools on the problem, but I casually imagine that they are dynamically loading a lot of libs, so a broken pipe or a dropped packet or two would certainly immobilize the UI until TCP/HTTP had gone through the dance of either resending the packets in question, or teardown/setup.
That said, the previous edition of Gmail -- possibly because it was lighter weight -- rarely misbehaved this way.
I believe we are seeing with gmail some of the current limits of the SPA designs. So it's not Google's fault, per se, and we should expect more and more sites to begin to evince the same drawbacks as the SPA model ineluctably takes over. (It really is superior.)
Eventually, problems in SPA will be resolved by improvements at the backend, on the wire, or by way of improvements to webpack, or the browsers themselves.
- TeMPOraL 8y agoSo basically, "wait for Moore's law to catch up", web edition? Your network connection might be aggravating the issue, as quick look at the Network tab show it issues a metric crapton of small requests (on my machine lasting for more than a minute after opening the page). But I do have a decent enough pipe, and still get ridiculous load time + performance problems. And so seem other people commenting here about performance. The problems of today's SPAs are mostly self-inflicted.