> On Oct 7, 2024, at 1:39 AM, Larry Garfield <la...@garfieldtech.com> wrote:
>
> On Sun, Oct 6, 2024, at 2:33 PM, Mike Schinkel wrote:
>
>>> On Oct 5, 2024, at 10:25 PM, Larry Garfield <la...@garfieldtech.com> wrote:
>>>
>>> A number of people are concerned that if we use any of the "Big Names", it
>>> would be interpreted as an endorsement of that project. Eg, if we rebuilt
>>> the main website using Laravel, the Symfony folks would feel slighted. If
>>> we used Symfony, the Laravel folks would get rather cross. If we used Yii,
>>> the Slim folks would get upset. If we used Drupal, we'd get constant "well
>>> why not Wordpress?" questions. Etc.
>>
>> OR, we could change the current model and consider and another approach.
>>
>> Instead of maintaining a website based on 1980s[1] technology which can
>> give newer developers who are interested in modern developer tools the
>> opinion that PHP is not for them, PHP could move to a model for its
>> website where it embraces "Big names" and does so on merit.
>
> *snip*
>
> While I am sympathetic to the idea of "if you want professional work done,
> just hire a professional," that is also vastly off topic for what we're
> discussing right now.
It is not off-topic, because it directly addresses the concern of mentioning or
not mentioning web frameworks and not using them for internal use.
> The scope at the moment is much more "can we *please* tell people to use
> Composer? Can we *please* use PHPUnit for writing PhD and not feel guilty
> about it?" It's much more pedestrian and practical for the time being.
However, yes, this point is completely valid, and can and should happen sooner
and with or without what I suggested.
-Mike
