I thought 'Fastmail' was a silly name until I logged back into Gmail.
And then waited for it to load.
And then waited for it to load.
Did you have a warm cache for either? I find that Fastmail’s cold load is generally a fair bit faster than Gmail’s cold load, and Fastmail’s warm load is consistently faster than Gmail’s warm load; but Fastmail’s cold load can be slower than Gmail’s warm load.
I’m looking forward to working on service worker code loading loading and offline support in Fastmail; I expect us to get warm loading to under one second on a typical desktop machine, regardless of location (because it will require no network calls).
Either way, once the code has loaded, Fastmail is consistently snappier than Gmail. And uses far less memory (in Firefox, 10–15MB instead of >150MB). Offline mode will improve snappiness even further even if you don’t opt into actual offline sync, by virtue of persisting its data record cache. But that’s not implemented yet.
I was interested in what front-end library you guys were using so I did a bit of searching and found a twitter post about OvertureJS. I know this is kind of random, but I'd love to understand how you guys came to the decision to build a framework from scratch instead of relying on Angular/React. What kind of technical limitations did they have that you guys wished to tackle with Overture?
When you care about performance, there’s still a lot to be said for controlling the full stack.