Yay, language war! j/k
If you'd prefer Python, that's fine, although I must admit I have no familiarity at all with Python so we'd probably have to adapt your existing code.
I chose PHP for a number of reasons, including: * I'm very familiar with it, and so are quite a few other people * There's a lot of code available for it to make complex tasks like RESTful web services really easy * It can be optimised to handle massive loads, even with the overhead * It's got a lot of data processing features inbuilt * There's already an edit counter in PHP ;) (mine)
On Nov 22, 2007 7:41 AM, River Tarnell river@wikimedia.org wrote:
draicone@gmail.com wrote:
Presuming it's going to be widely used, we might as well plan it here -- anybody else have structural suggestions for the tool?
at the risk of starting a language argument, i'm against doing it in PHP. i'd suggest Python:
- Lots of people know it (although perhaps less than PHP - but it's easy
to learn),
- It's fast, especially with FastCGI, compared to PHP, since there's no
startup cost on every request,
It's arguably a cleaner and nicer language.
There's already an edit counter in Python ;) (mine)
- river.
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/toolserver-l