I acknowledged there are workarounds/frameworks, and I especially recognized that modern PHP is often a different beast from classical PHP problems.
Ruby wasn't built to be embedded inside HTML, so I don't Ruby would have the worst problems of classical PHP even if Rails didn't exist, just as Perl (which both PHP and Ruby took inspirations from) even at its worst CGI architectures never quite had the same raw architecture problems that were rampant in early page-based mixed HTML and PHP design. The trade-offs for those architecture problems was development speed and "ease of use", PHP succeeded so well on the early internet almost precisely because of such problems.
ColdFusion too presumably succeeded as much as it did in Enterprise because of those problems in that space (easy to sprinkle a bit of server-side code in the middle of a page at will), though with no excuse for being free or easy to host. It's unfortunate that that also leads to the legacy of spaghetti code it will perhaps eternally have left behind in big-E Enterprise.
