I've also gone with Spark, after looking into the bunches of iOS mail clients. But I'm jaded now. Sparrow was independent, and good, and got bought and shuttered. Mailbox was independent and good, and got bought and shuttered. Spark is independent, and very nice, but it's free, and it'll get bought...and shuttered. :(
I like Google Inbox a LOT, but it doesn't have a unified mail interface, and if a million people don't use it every day, it'll probably get shuttered like Google Health and Reader did...
I'm just saying, don't get too attached to your email client, especially if it's not a profit center for the company making it.
Server-side access is what's needed in order to do push-notification based email updates, which is an important feature for me, and having written that code once or twice, I'm totally okay with that.
I'm getting more than 1M SHA1 + Hamming Distance calcs/core/sec on a Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, and I haven't really optimized beyond the obvious.
It's a brutally simple algorithm, really. XOR + bitcount, which only iterates for each 1 bit, so the lower the total hamming #, the faster it finds it.
It's in C, so everything works in unsigned long blocks. Compiled with -O3 it's:
real 0m0.968s
for 1M each on two forked processes, and 80 lines of code.
I like Google Inbox a LOT, but it doesn't have a unified mail interface, and if a million people don't use it every day, it'll probably get shuttered like Google Health and Reader did...
I'm just saying, don't get too attached to your email client, especially if it's not a profit center for the company making it.
Server-side access is what's needed in order to do push-notification based email updates, which is an important feature for me, and having written that code once or twice, I'm totally okay with that.