| PHP typically required a web-server, system administration which is old fashioned. No one wants to do that which is fine as it keeps me employed. When Ruby made western presence it was clunky. No one knew what it was and it got stuck with that personality. It had an ecosystem too but never hooked in to the western world. Java is tainted by Oracle and seen as "business". And it's also weird how Postgres has made an uprising appearance. It was sitting duck back in the 00's. I knew it existed because as an script kiddie I could install a php forum and select it as a database backend but I never did. Want to make a LCD display? You can simply by slapping a python library in to your code. Ecosystems pull coders in. Thinking about it, it's probably why Perl was popular before with CPAN. The old net was special but skills had to be learnt. Remember the days when you had one server for one service? The new net is terrible but everything is handed to you on a golden plate. |
IMHO deploying PHP to production is easier than Ruby/Python. You need a web-server but once it's configured (not a rocket science) you just copy all .php files. For ruby you also want to have a web-server (e. g. nginx) unless the load is negligible. If you want to deploy a project with all dependencies you probably need something like rvm but some gems would be easier to install form OS packages (like pg or other wrappers around C/C++ libraries installed from OS packages too). And then for ruby you need an additional daemon (HTTP) which will be restarted on updates (and auto-restarted if it will crash).