Now you might argue that some of those choices aren't that appealing, or that it's not guaranteed that someone else will pick up the app and run with it... but look at the scenarios with a closed-source, proprietary app: If the devs drop it, you're f%!#d, end of story.
I do wish companies that abandon projects would OSS them more often though.
Agreed. But to their credit, Google have some history of open-sourcing things[1][2][3][4], so maybe there's a chance that this product will be released as well. At least one can hope...
[1]: http://code.google.com/opensource/
[2]: http://code.google.com/opensource/projects.html
* without a corporate "sponsor" entity behind it. (Chromium => Google, etc.)
No it isn't. I didn't say that F/OSS is universally better than closed source, or anything crazy. I said that F/OSS has one specific advantage over closed-source, proprietary software, and that relates to the ability for a different group to continue development of a project that would otherwise be abandonware. Are you going to argue that this isn't the case?
No GUI-based F/OSS product has ever achieved the level of polish and usability of things like Sparrow because the people working on open source projects only want to do coding, they don't care about design, bug detection, documentation or, God forbid, user interfaces.
That's debatable, but it also has nothing to do with what I said. Yes, F/OSS has a reputation for being weaker on the UI/UX/design front, no one is contesting that, so far as I can see.
On the other hand I use a lot of OSS on servers and in the past on my workstations, and have modified them and fixed bugs and such. There are definite advantages but this particular one is not that useful on a large scale.
That said, yes, I agree that some projects would be difficult (maybe even impossible) to monetize as F/OSS. We know the enterprise stuff works, consumer apps may or may not be a different story. I think that book still remains to be written.
No you didn't. You bought. There was no investment, you should not expect a 'return'.
Even worse, I invested in Sparrow because I vastly prefer desktop apps like Sparrow to web apps like GMail. That's sad.
How is that "a few years"?
(Granted, October of 2010 still isn't ‘a few years’ a go.)
[1] http://blog.sparrowmailapp.com/post/1262858384/40-000-sparro...
[2] http://blog.sparrowmailapp.com/post/2497742134/150000dwnlds
The biggest concern I have with this is the same thing that happened to Tweetie: the one company that should have scooped it up did and then completely changed it into something that barely represented the existing app (and more or less dropped an interest in the desktop client).