The language you're using is going to be pretty agnostic to the performance of search.twitter.com. You're dealing with a loosely coupled architecture over an Internet WAN connection ... and nothing you do will change the base performance of search.twitter.com itself.
The specific API you select could be an entirely different story, but with a RESTful API, most APIs are going to have a hard time making performance mistakes. If you have a lot of client-side processing, C# may be your best bet on a Windows x86 or x64 machine, with Java equal, or a close second. (Java's only faster on Java processors, and really only at scale.) Any interpreted languages are going to have a much harder time doing in-memory or I/O bound work with the same level of performance, if that's what you're after. Thanks- - Andy Badera - [email protected] - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Tue, May 26, 2009 at 8:32 AM, Merrows <[email protected]> wrote: > > I have a system already written in C# and .NET which I started in > 2003. I have been happy with using c# and .NET as it has a good class > structure, and also Winforms works well for writing client-server > applications. Recently, I have seen much less interest in C# from > developers. > > I want to integrate search results from twitter into the current > system and I am thinking of what languages to use. > > I have googled what language to use, and the limits of JSON and ATOM > have placed some restrictions on what I can do. Especially, some > developers have complained about performance issues using C# and .NET > related to serialization of the data. > > Does anyone have any experience of Twitter API's and especially the > search? If so, are there are machine performance issues, or issues > with finding open source code? >
