Here’s two alternatives: 1. Don't write object oriented PHP. Despite the promise it showed early on, history now tells us that "Object oriented" is not a guara

Here’s two alternatives: 1. Don't write object oriented PHP. Despite the promise it showed early on, history now tells us that "Object oriented" is not a guarantee for quality, nor does it prevent spaghetti code. 2. Write framework-compliant object oriented code in another language/runtime more suited to executing it (basically anything that doesn't try to live directly inside the Apache request/response cycle). You might not consider them "good" alternatives, but I think they are the choices a lot of people eventually end up choosing between. I generally agree that frameworks are good to use for saving developement time, but execution time matters. The performance penalty paid for some of these frameworks on PHP compared to the two alternatives above is large enough to negate the benefit for all but trivial cases.