Gmail is _fast_. The browser doesn't reload when you navigate around and when you click on something it gets loaded very quickly. You can't just put a shiny UI in front of an IMAP server and get this sort of functionality, you have to write your own mail server with a rather intense database backing it. I have 70,000 emails spanning a decade (mostly useless) and searching is a breeze. Everything works fine and quick with a huge volume of data. When I send messages they're actually sent in a second or two, when I click next message the next message appears in a fraction of a second. The UI is the frosting on the cake. It's critical that it's very fast, but the underlying mechanics have to be very fast too, and that's not just a manner of copying pixels.
It is fast when a huge amount of JS gets loaded and latency times are low. But with high latency? A horrible experience and if it even works I'm grateful.
It is pitifully slow when on a limited connection. And the contortionist-like procedures needed to log in from an unfamiliar IP don't make it slow, just largely non responsive.
Have you tried FastMail? They use Cyrus...
> you have to write your own mail server
... but I concede they (FastMail) do sponsor most of Cyrus's development.
I think you deleted the last "."
While it would be quite straightforward to clone an almost pixel-perfect version of Gmail, there is something in hacker culture that makes this kind of project unattractive. I don't really understand why.
Instead what we end up with when someone starts a new mail app is some half-cocked design that makes sense for that particular user, who is always an engineer, and the result is suboptimal for pretty much anyone else.
So the project fizzles and dies before it even gets started. This happens over and over again even for larger and more visible projects like Mailpile