3 ms·
"WSGI in Python gets you part of the way there, but you still need to import a library to talk to the server. This makes PHP just plain easier to get off the gr
by monkeyfacebag 15y ago
"WSGI in Python gets you part of the way there, but you still need to import a library to talk to the server. This makes PHP just plain easier to get off the ground for web applications."
The first sentence is mostly accurate, but I disagree strongly with the assertion in the second sentence. Grouping related functionality into libraries reduces the cognitive load of programming. The same could be said for his assertion about the benefits of HTTP as a "first-class citizen."
I do agree that getting a PHP application running on a LAMP stack is easier than say getting a WSGI implementation up and running, but this has nothing to do with libraries.
- ircmaxell 15y agoMy intention was the full process from creating the first file, to getting a server to serve the content is far easier to do in PHP than Python (granted, in Python it's pretty much boilerplate, but there's a lot more than needs to happen). As far as the benefit of first-class vs libraries for handling the request, that's something to consider (as there are arguments on both sides)...
- drivebyacct2 15y agoThat was pretty thoroughly discussed in the original thread. Yes, PHP throws everything you can do into functions in global scope. It's "convenient" but it's messy. It's also, correct me, but an incredibly trivial distinction.