I prefer PHP but as glue. Like my first-grade teacher taught us, a drop of glue goes a long way. Too much glue makes a mess. Unlike many programmers, I don't p

I prefer PHP but as glue. Like my first-grade teacher taught us, a drop of glue goes a long way. Too much glue makes a mess. Unlike many programmers, I don't pick one of the Turing-complete programming languages (PHP, Python, Ruby, Go, whatever) and try to write as much of my app as possible in it. Because they are Turing complete, you really can write everything in it. Because you can learn only so much, you are tempted to write more than you should in that language. But like I said, PHP is just a part of my stack, and I try my best to make it one of the thinnest layers. The other parts are Postgres, Apache, and the user's browser. I try to use each of those as much as possible. The server operating system also plays a part, and I suppose my stack includes Bash. Basically I try to do as much business logic as possible in Postgres. This leaves PHP to do little more than glue the output of Postgres to HTML templates.