On 3/28/10 10:49 AM, Matt Lee wrote:
On 03/28/2010 07:42 AM, Henry Litwhiler wrote:
The Python application wouldn't display things to the browser, and I'm
not saying that we use Python to replace PHP's role as our web
application language - instead, we can use it to manage the backend
communications between GNU Social users.
What backend though? The user must be able to run a complete GNU social
system in a browser, on commodity web hosting, in PHP.
I don't see what Python can do that PHP can't.
Python is, subjectively, a better language, and ought to be used as much
as possible (though not in roles that it is not suited for). I say
subjectively because it really is a matter of opinion.
Python is *far* more suited for running as a desktop application than PHP.
I also don't think that we're on the same page when it comes to
commodity web hosting. While users should be able to outsource their GNU
Social install to ensure maximum uptime, making it so that the exact
same GNU Social application runs on both personal and commodity hosting
shouldn't be a priority. We can have one version of GNU Social for
people who want to run it on an outsourced server, and one version for
people who want to run it at home.
Since (generally) PHP code only runs when a user accesses it via the
browser, making the install continuously receive and send out data would
be quite a task indeed, if done entirely in PHP.
--
Henry L.
