|
What made you guys choose Python for making OSQA? Why not php/ruby? |
|
I'm very happy that we use python/django and not PHP (god forbid me) or ruby. Python is a great language, is the fastest interpreted language out there, with a big connection with C (actually most stuff in the Python standard library is written in C). Ruby is nice too, but not so mature. Ruby benefited from Rails but with Python/Django it was the other way around, Django benefited from Python. And Django is a powerful/feature rich/well written framework. Most of the members on the team /including me) have a big Java background, and at some point we started to plan a switch, but we quickly gave up in favor of this great framework. 2
Agreed. Very well put. I'm a big Java guy too, but I really have to thank you because OSQA has been my first exposure to Django and now I'm really excited about both OSQA and Django. Django really is a fantastic framework.
(23 Apr '10, 13:11)
Zuhkov
|
|
The short answer to that question is that OSQA is actually a fork of CNPROG, a Chinese-developed SO clone. CNPROG was written in Python/Django, so OSQA is as well. There are actually SO clones written in Ruby and Drupal (PHP). I believe the Ruby one is called Shapado and the Drupal one is called ArrayShift. Based on what I've seen and my own experimentation, however, OSQA is in the best shape of the three, by far. |
|
|
|
OSQA is a fork of CNProg which is built on Django. The choice probably wasn't what language to use but which framework to use. That choice dictates what language to use. Django has been around for a while and is one of the more popular frameworks. More information on Django can be found at http://www.djangoproject.com/ |
