Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99402 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16573 invoked from network); 6 Jun 2017 15:19:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jun 2017 15:19:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:49497] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 32/60-27119-F08C6395 for ; Tue, 06 Jun 2017 11:19:44 -0400 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3whwMv5BHpzXMk for ; Tue, 6 Jun 2017 17:19:39 +0200 (CEST) To: internals@lists.php.net References: <5313411f-40b4-58c6-83a8-7e813526f2a7@tekwire.net> <12948b4b-bd2d-b88e-80a0-f70ba2d49657@fedoraproject.org> <5e8464ca-8fa1-ad0c-c296-36ed1b6bd2a3@tekwire.net> <05d8f04a-4fad-fbee-4bc5-bf85f282212c@rhsoft.net> <1de8757c-6f4e-33d0-e333-9c1dd6f66e3a@rhsoft.net> <3E2E2294-1A2B-4857-81BC-6A1B0824B53F@gmail.com> Message-ID: Date: Tue, 6 Jun 2017 17:19:39 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <3E2E2294-1A2B-4857-81BC-6A1B0824B53F@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Proposing inclusion of PCS in the 7.2 core distribution From: lists@rhsoft.net ("lists@rhsoft.net") Am 06.06.2017 um 15:33 schrieb Rowan Collins: > On 6 June 2017 12:27:16 BST, "lists@rhsoft.net" wrote: >> looking at the code quality (style, readability, robustness, >> error-handling) of 99% of php userland code out there - which is >> horrible to say it nice - even if all that is true i still doubt that >> it improves quality in the long term, sometimes it's better working >> things are not maintained then badly maintained > > There is no reason to assume either that we would attract the worst possible PHP programmers, or that we currently attract the best possible C programmers. Indeed, it's likely that a lot of existing extensions have poor style, lack of robustness, etc, because they were written by people "speaking a second language", i.e. PHP programmers trying their hand at C. > > I'm not even sure your last sentence is true very often - changes to the core require changes to extensions, so either the entire core stagnates (in fear of breaking things) or extensions get abandoned (because rather than working but unmaintained, they are now broken and unmaintained). > > There are certainly details to be worked out, but I think the principle of making it easier to build and maintain a rich core library is a very good one that's all nice but in this thread even "composer" was brought once again to the game - frankly making composer mandatory will lead to put a lot of things require it on a blacklist for a many people because i am pretty sure speaking in this context for a silent mass (just the offlist responses on other threads where i called composer a red line for me with the summary "and i thought i am the only one" are enough to back this up) where will this php scripts stored - how do they deal with openbasedir - do you need to place their location in openbasedir while you normally avoid to add anything oustide your application there - and so on