Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123951
Message-ID: <9d3e9063-aecf-4c56-a17d-782e7a60fed2@bastelstu.be>
Date: Thu, 27 Jun 2024 20:24:01 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Static class
To: Stephen Reay <php-lists@koalephant.com>,
 Mike Schinkel <mike@newclarity.net>
Cc: Claude Pache <claude.pache@gmail.com>, ayesh@php.watch,
 Bilge <bilge@scriptfusion.com>, 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>
Content-Language: en-US
In-Reply-To: <DB280533-7FBE-41CD-B841-9BB163A75280@koalephant.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/25/24 05:17, Stephen Reay wrote:
> and I'd rather have the feature with slightly odd syntax rather than not at all.

Absolutely not. PHP is already odd enough as it is. We should not add 
additional oddness in the interest of pushing a new screw-shaped feature 
in with a sledgehammer. Any additional oddity makes it harder for Junior 
developers and developers coming from a different language to learn PHP 
and also required the developer to learn the language details by heart 
instead of being able to rely on their intuition.

I'm already leaning towards "Don't want static classes", but if they use 
an attribute instead of a keyword, then it's going to be a clear "no". 
See also my email in response to Ayesh.

Best regards
Tim Düsterhus

PS: Can you please cut the quoted parts to a minimum instead of 
including the original email in full? That makes it much clearer to see 
what part you are actually replying to and reduces the amount of storage 
requiring for all the thousands of ML subscribers :-)