I'd call what you have some excellent skills. Legacy code would be difficult for a lot of folks to manage. I would deffo augment your skillset with the latest and greatest simply for your own benefit. There's a lot of great additions and it gets better with every release. OOP is excellent, it's allowed me to keep my sanity by abstracting away garbage code at work into something tangible, reusable and clean. I've published my own composer packages and it's a world of difference having the ability to write some code, test it, publish it, install it as a dependency and never have to worry about it again for the most part. It's helped me reduce project's metal overhead, strengthen my coding standards allow others to benefit from my designs. The main difference is heavy reliance on OOP and strong type enforcement. Basically designing things so they less susceptible to errors, and more robustly designed systems overall. The toolsets and composer libraries are amazing. Lots of reliance on shell commands to generate code, run tests, compile assets, lint code etc. Everything is streamlined once you've gotten familiar with the tools you can use. I love Laravel because they give you a complete ecosystem to work with. I get the Dev Server, Asset Compiler, Framework, and Paid Services if I want them. They've made it really easy to write and deploy modern PHP. My job used to be a headache and now it's very smooth sailing thanks to Laravel. More on reddit.com

Probably no significant improvements, since most of the time is spent waiting on MySQL and the file system. I’d love to be surprised, but right now my expectations are low.

It’s still exciting because it could open up new areas to PHP that used to require custom extensions.

More on reddit.com

Just curious: Where did the tests originate from? (Is it possible network latency affected the results or was it all local?) More on reddit.com

Thanks for writing this krakjoe!

I'd especially like to emphasize the awesomeness of point 1: You probably heard many people tell you that PHP does not support multi-threading whereas Ruby and Python do. In a way, the converse is true: PHP has support for actual multi-threading, whereas Ruby and Python implement it using a GIL (global interpreter lock, which basically means that threads can only improve performance if they are IO-bound). PHP just doesn't natively expose threads to the user and requires an extension like pthreads instead.

More on reddit.com