A lot of the old guard of PHP left it behind for a few reasons...
PHP 6: A lot of php devs in the frankenPHP thread took issue with me mentioning this because it never launched. A lot of devs shook their head and moved on after 6 got shit canned. After having gone through PHP 3-4-5 change where we got all the juicy OOP features, while watching python 2-3 flail we realized that we had been sold a future that did not exist. Python 2-3 took the UTF8 hit, the fact that PHP wasnt going to was a sign that we were going to be stuck with MB string bs for a long time if not forever. There's a lot of folks that went to python when 6 got canceled and didn't look back.
Reuse of code: in this regard python and ruby were in a much better place for web code to be reused in CLI scripts, Workers, jobs... hell python ended up in a million other places cementing its win over ruby. This same "one language everywhere" mentality is why you see a lot of server side JS on the web.
While most of the PHP devs who were my peers at the time went to python or node I ended up picking a very young Golang. It has been a decision that not only did I not regret but a lot of those python/node devs are asking me how to bootstrap their golang experience.
Go, brings me the joy that early PHP4 did. When you just shoved a .php file onto a server. I get that same feeling when I ship out a product that was just the standard lib in go, or where I add in a bit of Postgres... That can be the whole stack for a working API... Mix in hmtx, maybe you want to use fancier templates (templ is one people like). I dont need a stack to do a project, my project dictates what I use, and candidly its very little.
The frankenPHP thread and then this: https://news.ycombinator.com/item?id=40543438 popped up in the last week. Now your here pitching this...
A lot of the old guard of PHP left it behind for a few reasons...
PHP 6: A lot of php devs in the frankenPHP thread took issue with me mentioning this because it never launched. A lot of devs shook their head and moved on after 6 got shit canned. After having gone through PHP 3-4-5 change where we got all the juicy OOP features, while watching python 2-3 flail we realized that we had been sold a future that did not exist. Python 2-3 took the UTF8 hit, the fact that PHP wasnt going to was a sign that we were going to be stuck with MB string bs for a long time if not forever. There's a lot of folks that went to python when 6 got canceled and didn't look back.
Reuse of code: in this regard python and ruby were in a much better place for web code to be reused in CLI scripts, Workers, jobs... hell python ended up in a million other places cementing its win over ruby. This same "one language everywhere" mentality is why you see a lot of server side JS on the web.
While most of the PHP devs who were my peers at the time went to python or node I ended up picking a very young Golang. It has been a decision that not only did I not regret but a lot of those python/node devs are asking me how to bootstrap their golang experience.
Go, brings me the joy that early PHP4 did. When you just shoved a .php file onto a server. I get that same feeling when I ship out a product that was just the standard lib in go, or where I add in a bit of Postgres... That can be the whole stack for a working API... Mix in hmtx, maybe you want to use fancier templates (templ is one people like). I dont need a stack to do a project, my project dictates what I use, and candidly its very little.