Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110079
References: <05D65F68-662F-4AE4-8D84-25B1D4279420@newclarity.net>
To: PHP internals <internals@lists.php.net>
Message-ID: <d68311d9-8966-fd03-533a-4af2789801a0@gmail.com>
Date: Thu, 7 May 2020 19:38:20 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0)
 Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <05D65F68-662F-4AE4-8D84-25B1D4279420@newclarity.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] A Standard PHAR library included with PHP?
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> One of the primary reasons for many of us — or at least me — to want 
> more things in core is not listed above, and that reason is:
> 
> - Standardization

Core and standardization are completely different things. There are a
lot of things in PHP that are being standardized out of core, and
putting something into core just for standardization is the wrong place
to do it.

To me, this feature clearly looks at something that belongs to
userspace, and magic that it introduces looks like it shouldn't be in
core but in some kind of module, or even better, IDE. Putting sematic
features like deprecation into runtime is not right, if deprecated code
got into runtime, putting out a warning each time it is run is useless.
If nobody looked at these warnings before they got to production, surely
nobody will look at them after.

-- 
Stas Malyshev
smalyshev@gmail.com