#Tidelift lowers the amount paid out to #PHP package maintainers because demand with enterprise app developers is low.
Received the following in an email:
“Unfortunately, the reality is that we haven’t had as much traction with enterprise app developers using PHP as we have with other ecosystems; our customers tend to build their applications with mostly Java, JavaScript, and Python with smaller amounts of C# and Go. (1/3)
@Aedius@ramsey Symfony is usually pretty fast in benchmarks, unless you're doing something dumb with it. Last I saw the event system was still not as fast as Tukio, but then nothing can be. 🙂
(I've no idea if one could drop-in replace Symfony/EventDispatcher with Crell/Tukio. They're both PSR-14, but have different registration APIs. Maybe bridgeable?)
(Be glad it's not Laravel. There's inefficient for you.)
It's fast until you have a monorepo, with 6 websites, two db kind, some layer are shared some not, but they are all configured per websites, for 8 years across many version upgrade.
We have started to remove some part of the repo, but for many of my colleagues Symfony is a religion ...
@Aedius@ramsey Woof. See previous statement, "unless you're doing something dumb with it." 🙂
Even the Symfony core team would (last I checked) say most of your business logic should be framework agnostic. Sounds like someone is using Symfony wrong.
Yes when we try to bend something, we can do whatever.
But it seems completely the Symfony way to call a function in the template, that load a service that is decorate by another that do SQL queries and publish internal event that are listen somewhere else in the application to override the result.
@Aedius@ramsey I mean, a framework build on pull based components is fine. That can be done well, IMO, and I'd frankly like to build it someday. :-) But that's not how Symfony is supposed to work.
“As a result, we will be reducing the income for #PHP packages to a base level of $25/mo per package. This is more in line with other ecosystems where we have limited customer demand. These changes will go into effect with the next lifter payout on April 3rd. (2/3)
“I realize this may be unfortunate news for you, as this income has been steady over the last several years. If you have any questions for me, I’d be happy to answer them, and certainly as we see more customer demand for #PHP within our customer and prospect pool, that will be accompanied by a corresponding increase in the income provided to PHP packages.” (3/3)
Add comment