Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99950 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99842 invoked from network); 19 Jul 2017 20:16:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jul 2017 20:16:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 84.19.169.162 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 84.19.169.162 mail.experimentalworks.net Received: from [84.19.169.162] ([84.19.169.162:52960] helo=mail.experimentalworks.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BD/EE-02884-53EBF695 for ; Wed, 19 Jul 2017 16:16:54 -0400 Received: from kuechenschabe.fritz.box (ppp-46-244-182-12.dynamic.mnet-online.de [46.244.182.12]) by mail.experimentalworks.net (Postfix) with ESMTPSA id 821CE5ED5B; Wed, 19 Jul 2017 22:16:49 +0200 (CEST) Message-ID: <1500495408.16819.37.camel@schlueters.de> To: Mathias Grimm , Andreas Heigl Cc: "internals@lists.php.net" , Sara Golemon Date: Wed, 19 Jul 2017 22:16:48 +0200 In-Reply-To: References: <78DFA5C9-5C49-4B75-8FC0-C0945FD85694@heigl.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] php.net website From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Mi, 2017-07-19 at 21:34 +0200, Mathias Grimm wrote: > Thats a valid point but that can be addressed in some nice ways. > > The documentation can mention it somehow and that doesn't mean > somebody else should use that framework/lib for every project/case. > That would be similar to saying that we prefer Linux over Windows, > just because we use Linux hosting and better would be to instead > build our own operating system, just so that people don't get > inclined to one side or another > A bit of a stretch of an analogy but more or less the same idea. > > The fact that we use some well known framework/package would reduce > the barrier to get more people involved in the project, now and for > the future. Not using them is going back to 2005 when everybody had > their own framework. > > I am not suggesting any framework in specific but think there as some > good options out there. We would be quit well served with a micro- > framework as we basically need just some kind http stack + routing, > but that is deep down the execution plan discussion. Mind that the php.net site except for the doc search actually is a static web page we could also generate completely as static HTML. This is not a complex system where any "business logic" does complex stuff, thus a framework doesn't help much, while bringing complexity. johannes