Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100029 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24985 invoked from network); 24 Jul 2017 09:51:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jul 2017 09:51:18 -0000 Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.216 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.216 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.216] ([81.169.146.216:36184] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D7/CB-18680-513C5795 for ; Mon, 24 Jul 2017 05:51:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1500889874; l=6656; s=domk; d=kelunik.com; h=Content-Type:Cc:To:Subject:Date:From:References:In-Reply-To: MIME-Version; bh=bNsx34AtiEvxduBwM5jOiGa6/Q1chmxXXf7MyKHFYIY=; b=nSc46OPq1iGhJ3+HqRB/XUrNX1p/xk0W1QKrn1sP2l2Yg5Bno1LMr5XIPbT7Hm4vxm Dd7oMdHhgy/DDeyJz7ExIKqMZeJtVcU25I3ACpc9y/t7XJvnqLtOBNHfJJuLVf6Iva2Z luNWwVla7J3MUaHK0CtmhP0rJ25u9RSvkO+OU= X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mls2vWuiu+7SLDup6E67mzuoNHBqT83Q== X-RZG-CLASS-ID: mo00 Received: by mail-oi0-f54.google.com with SMTP id a9so19744545oih.0 for ; Mon, 24 Jul 2017 02:51:14 -0700 (PDT) X-Gm-Message-State: AIVw110MUXTNw73OoKK2tdV5UqTb8ODEmmK96pV7fWvSVfxDyD7mT0ht 0PYClLCgX3SK0L2/JcB01ppwKmSR6A== X-Received: by 10.202.235.19 with SMTP id j19mr7916128oih.15.1500889873859; Mon, 24 Jul 2017 02:51:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.154.167 with HTTP; Mon, 24 Jul 2017 02:51:13 -0700 (PDT) In-Reply-To: References: <1500551058.16819.47.camel@schlueters.de> <1500584492.16819.71.camel@schlueters.de> <1500847438.16819.86.camel@schlueters.de> Date: Mon, 24 Jul 2017 11:51:13 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Kalle Sommer Nielsen Cc: =?UTF-8?Q?Johannes_Schl=C3=BCter?= , Mathias Grimm , Sara Golemon , PHP Internals Content-Type: multipart/alternative; boundary="001a113cf052c74d2105550d2719" Subject: Re: [PHP-DEV] bugs.php.net website From: me@kelunik.com (Niklas Keller) --001a113cf052c74d2105550d2719 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2017-07-24 10:15 GMT+02:00 Kalle Sommer Nielsen : > Hi Johannes > > 2017-07-24 0:03 GMT+02:00 Johannes Schl=C3=BCter > > It is also good for the PHP ecosystem at large to show we're using > > libraries, where it makes sense. If we use a variety we're also not > > favoring single ones :) > > As much as I agree with that, I do not see a big thing that using a > library makes it much easier to do for a bug tracker that fits our > needs. Okay maybe a captcha or SSO, but the rest can be done in a > simple encapsulation that we don't need thousands of lines of code > just to implement something so basic. > > > A reason for this is that these sites are not "actively developed" and > > it should be possible to find the relevant code within a few minutes, > > even when looking at it every second year or though. With the current > > architecture I go to search.php's code and can see what's going on. > > With a framework I have to see how the framework handles the routing > > and where the relevant controller is and so on and so forth ... this > > is contrary to other projects under constant development possibly by > > larger teams and is also different from developing a generic bug > > tracker (or whatever site you look at) where things need to be > > configurable for different usage scenarios ... > > I think the main reason for these sites not being actively developed > is that they do their job, I did some minor cosmetics to the bug > tracker, but besides maybe better integration with github PR's, I > can't see that many more features our tracker needs. > > I get that with a framework it makes the debugging route easier or if > you are just curious to study the code, and we can still achieve that > with simplistic encapsulation where it makes sense. If we keep your > example with search, what we can do is to implement functionality that > returns records based on criteria, we need that functionality in > multiple places anyway. > > I always saw the PHP project as an example to how powerful the > language is by its own, out of the box and I will continue to advocate > for us to continue that way It's unmaintained code, nobody wants to touch it. Any attempt to improve anything doesn't go anywhere, because there are too many people saying the current state is fine. See https://github.com/php/web-bugs/pull/26 for an example. There's no need for a framework, libraries are just fine. But saying that the PHP project is a good example for how powerful the language is, is ... really strange. The attitude of "don't change anything, it's fine" makes it really hard to find motivation to contribute anything. Regards, Niklas --001a113cf052c74d2105550d2719--