architecture - C# Twitter API, use or not a wrapper? -


should using wrapper library twitter's api, or build library of own?

my application needs connect twitter read status updates other users, , doesn't need post updates, or send twitter kind of messages.

update application resource intensive, every "small performance gain" potential huge performance gain in future. also, i've read, tweetsharp going discontinued?

assuming can find easy-to-use library has been well-tested others, why want spend time building part yourself, when time spent building real app?

just because won't use all of api doesn't make worth building own library, imo. don't reinvent wheel :)


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -