Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124105
Message-ID: <e587554b-f24c-49fe-8658-3c15b15cc615@bastelstu.be>
Date: Sun, 30 Jun 2024 17:10:27 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Static class
To: Bilge <bilge@scriptfusion.com>, Stephen Reay <php-lists@koalephant.com>,
 Mike Schinkel <mike@newclarity.net>
Cc: Claude Pache <claude.pache@gmail.com>, ayesh@php.watch,
 php internals <internals@lists.php.net>
References: <eb3f59cc-3ed8-461a-a3a4-f6ba10ed31e1@scriptfusion.com>
 <88D83E92-94BE-4548-B398-8F5C74765FFD@gmail.com>
 <882BD9E0-42E9-4C84-A144-7C1DFC4CE5EB@newclarity.net>
 <DB280533-7FBE-41CD-B841-9BB163A75280@koalephant.com>
 <9d3e9063-aecf-4c56-a17d-782e7a60fed2@bastelstu.be>
 <d075222b-0c71-4ec6-8a2d-fdaba8a727c2@scriptfusion.com>
Content-Language: en-US
In-Reply-To: <d075222b-0c71-4ec6-8a2d-fdaba8a727c2@scriptfusion.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 6/28/24 21:29, Bilge wrote:
>> I'm already leaning towards "Don't want static classes"
> 
> Why? It is important to understand what your misgiving are in case there
> anything we can do to assuage them.

I don't see value in being able to explicitly mark a class as `static` 
for the reasons that have already been brought forward by other 
participants (such as Larry).

But more importantly, the RFC and discussion so far don't really 
convince me that any of the participants in favor of static classes 
really know what they want and thought about *all* the implications of that.

I strongly favor an opinionated RFC where the RFC author did their 
research and makes it clear why the proposal is the right choice and 
backs this up by proper arguments. Of course this doesn't mean that the 
RFC author should not listen to the list discussion, but the high level 
details should be clear right from the beginning. As of now the RFC 
still has some open questions regarding "core functionality" and even 
intents to leave them as a secondary vote.

In other words, too many cooks spoil the broth.

Given the upcoming feature freeze, the current list volume and core 
folks being busy with finishing up and polishing their own RFCs for PHP 
8.4, the timing doesn't really help getting the necessary attention 
towards your RFC either. I might be more receptive towards a quieter 
period of the year, where I can take the time to really think about the 
RFC, like I do for other RFCs as well. My earlier responses towards the 
Lazy Objects RFC might be a good example towards the level of detail I 
try to give RFCs. Even when I don't personally understand them or don't 
see myself using them (yet), I want a best-possible result that will not 
cause sadness 3 years down the road.

Best regards
Tim Düsterhus