Linked by David Adams on Sun 6th Nov 2011 04:35 UTC, submitted by twitterfire
Permalink for comment 496118
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2010-01-21
That's all well and good for you, but I have a fairly strict policy to only rely on web applications if they inherently do something that's not feasible to do natively.
Google or LibraryThing or Last.fm are, by nature, tools that get their value from their network effects, so I'll excuse that.
However, I'm now willing to commit myself to so many single points of failure (network connectivity, continued interest in the product on the provider's part, provider uptime, potential differences of opinion regarding the importance of various potential features, etc.) for an application for which the only benefit of being in the browser is that I don't have to worry about my update manager distracting me with a password prompt.