asked on

Choosing a Server-Side Scripting Language - Criterion 3

I’m spent the last couple years building a platform based on ASP.NET, and I’ve come to the conclusion that it’s not right for my needs. I’ve thought hard about making the leap to PHP, but I want to do so with my eyes open. Ruby seems like a reasonable alternative, as does Python. (Who knows, there may be another option that I’ve failed to list.)

I've broken this question into several parts simply because it's so big. This is my third criterion:

Criterion 3 – I’d like a server-side scripting language that is compatible with as many database formats as possible. (While I’m not crazy about Microsoft’s ASP.NET, I love SQL Server and would like to have the option to continue use it).

ASKER CERTIFIED SOLUTION

Aaron Tomosky

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Ray Paseur

What AaronTomosky said. No points for this response, please.

pepr

Django (Python) supports sqlite3, MySQL, and PostgreSQL. However, there are people who work also with MSSQL.

SOLUTION

Aaron Tomosky

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

pepr

Another decision criterion could be the reusability of the existing and of the gained knowledge, respectively. It depends on whether you already have developers for the project and if they know one of the being chosen languages. Otherwise, PHP is a web language, Ruby and Python are general languages (their knowledge is usefull on its own for other purposes). I cannot speak for Ruby, but Python is very nice and very practical language.

jdana

ASKER

aarontomosky - The abstraction layer recommendation is a great one. I've started looking into it. I also appreciate the REST / SOAP comments.