PHP in templates is so last decade
Release parity with WordPress achieved, check.
bert@jessie:~$ ab -n 1000 -c 10 http://localhost/projects/textpattern/
Document Length: 11769 bytes Time taken for tests: 6.104 seconds Total transferred: 12010000 bytes Requests per second: 163.82 [sec] (mean) Transfer rate: 1921.36 [Kbytes/sec] received
bert@jessie:~$ ab -n 1000 -c 10 http://localhost/projects/wordpress/
Document Length: 11289 bytes Time taken for tests: 27.320 seconds Total transferred: 11536000 bytes Requests per second: 36.60 [sec] (mean) Transfer rate: 412.36 [Kbytes/sec] received
Default installs, no tweaks other than to change Textpattern’s production status from “Testing” to “Live”, which should be the default IMHO.
Textpattern is in an enviable position, it’s magnitudes faster than WordPress, all it needs is a makeover. A new look for the TXP backend, with user friendliness in mind, and there’s nothing that can really stop it from gaining ground.
What can WordPress do? Rethink the loop? Take PHP out of templates? It really can’t do anything for risk of disturbing their fragile ecosystem. It’s stuck by it’s own meteoric rise to fame, a sitting duck I tell you.
Thanks goes to Team Textpattern, this point release is much appreciated.
Anything you can be, I can be greater!
Sooner or later I’m greater than you!