You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just migrated to Frankenphp as many in the Laravel community is doing now and it will only grow as it now has first party support by Laravel, even though it's still in beta. But it's the most performant combo.
And it uses a ZTS compiled version of php and according to the creator is has use that.
So therefor I'm asking if you can reconsider the dropping of ZTS support and making it supported again? As it will be a bottleneck for a lot of Laravel users moving forward so they cannot continue to use New Relic as a service, and we are one of them.
The text was updated successfully, but these errors were encountered:
I cannot find resources explaining why ZTS was removed. The maintainer of Frankenphp did explain why ZTS is a requirement for FrankenPHP
What do we need to get a ZTS build? Or is there a technical reason why it cannot be created anymore? In that case one have to choose for FrankenPHP XOR NewRelic.
I'm also curious why New Relic dropped support for ZTS, nowhere in your docs do you explain why it was dropped. My company is looking to move to frankenphp to benefit from the performance boost it'll give us.
I just migrated to Frankenphp as many in the Laravel community is doing now and it will only grow as it now has first party support by Laravel, even though it's still in beta. But it's the most performant combo.
And it uses a ZTS compiled version of php and according to the creator is has use that.
So therefor I'm asking if you can reconsider the dropping of ZTS support and making it supported again? As it will be a bottleneck for a lot of Laravel users moving forward so they cannot continue to use New Relic as a service, and we are one of them.
The text was updated successfully, but these errors were encountered: