What ongoing work does an email client need, though, besides fixing bugs and very occasionally adding new login protocols?

▲

asdewqqwer 6 hours ago | parent | next [-]

If you ever try to write a email client, you will immediately realize how difficult, if not impossible, to fix all the bugs for a email client. It is a multi-different-protocol-version-async-client-handling-same-database-with-thousands-of-race-condition backwards compatibility nightmare.

Writing a email client with support of just up-to-date protocols and assume it is the single client that will operate that account is trivial, write one that covers all corner cases is a totally different story.

▲

fluoridation 5 hours ago | parent [-]

I don't know about the rest, but surely the race conditions are the fault of whoever designed the concurrency part. An email client does not inherently have race conditions.

▲

asdewqqwer 5 hours ago | parent [-]

> assume it is the single client that will operate that account

You are still making wild assumption without actually thinking about what means to writing an email client.

	▲	fluoridation 5 hours ago \| parent [-]
		OK? Sure would be nice to hear why having a second email client talk to the remote server introduces race conditions on the local client (EDIT: that is, race conditions that are the local client's responsibility).

▲

ForHackernews 6 hours ago | parent | prev | next [-]

Adding a mobile version, MS Exchange integration, supporting OAuth2 login, refreshing the UI periodically because otherwise everyone whines about how "dated" it looks.

▲

AlienRobot 6 hours ago | parent | prev [-]

Their RSS could use some improvements, but the same could be said about all of them.