The real reason we’re upset about Sparrow’s acquisition

Re:The real reason we’re upset about Sparrow’s acquisition by albertzeyer on Saturday July 21, 2012 @08:57AM (#4274686)

Obvious thing: Some security vulnerability is found which gives attackers access to your system or so.

Or: There is some bug which gets active let's say after year 2013 or after 10k mails or so.

Or: (I don't know Sparrow so not sure if this applies.) You have created/build some app-specific content/database (like have done all your mail tagging with Sparrow) so you want to re-use it on future Apple hardware. Now assume that Apple introduces some new architecture (like an ARM MacBook) or makes some incompatible API changes in future MacOSX versions. Either you can't upgrade your hardware/OS or you will loose the app-specific work.

Etc.

[ Parent | on HN ]

Re:The real reason we’re upset about Sparrow’s acquisition by fallenhitokiri on Saturday July 21, 2012 @11:59AM (#4275021)

Everything valid - but as time passes there is sometimes just no way around upgrading your software. The fact that there could be an immediate problem was ignored by me, that's true.

Since they want to keep it alive (in its current state) I believe they'd fix something critical.

[ Parent | on HN ]

Re:The real reason we’re upset about Sparrow’s acquisition by spartango on Saturday July 21, 2012 @10:16AM (#4274802)

The first two are valid, but in the specific case of Sparrow, all the "state" is held in the mail provider(GMail via IMAP) or FB, which is nice.

[ Parent | on HN ]