Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Should I be using a wrapper library for Twitter’s API, or just build a library of my own?
My application only needs to connect to twitter to read status updates from other users, and it doesn’t need to post updates, or send Twitter any kind of messages.
Update this application is very resource intensive, so every “small performance gain” now is a potential huge performance gain in the future. Also, from what I’ve read, TweetSharp is going to be discontinued?
Assuming you can find an easy-to-use library which has already been well-tested by others, why would you want to spend time building that part yourself, when that time could be spent building your real app?
Just because you won’t use all of the API doesn’t make it worth building your own library, IMO. Don’t reinvent the wheel 🙂