By 'the-basics' I was simply trying to say that a purely functional approach for any existing PHP implementation, whether it is a CMS, framework, application, e

By 'the-basics' I was simply trying to say that a purely functional approach for any existing PHP implementation, whether it is a CMS, framework, application, etc. could help restructure the underlying architecture for whatever was originally implemented in straight PHP, somewhat like an API on the go. . .PHP has materialized some marvelous yet convoluted projects whose origin was not to solve a problem, but to do something very particular using HTTP, which at it's core, is what PHP does best. I dunno, I guess I just think a functional paradigm could offer a faster and easier way for retooling existing PHP applications/frameworks that focus on what the application is supposed to do rather than how it's going to do it. Let PHP's extensive library worry about the system's protocol; this could help leverage your end-product as an API first, rather than opting-out of any further abstraction just to get what you think you want. I dunno, I could be way off; I just think PHP is so matter of fact that attempting anything as abstract as what a purely functional language is capable of is nearly inexpressible.