Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94656 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34861 invoked from network); 23 Jul 2016 20:11:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2016 20:11:54 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.176 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.176 mail-pf0-f176.google.com Received: from [209.85.192.176] ([209.85.192.176:33049] helo=mail-pf0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A3/C4-05797-98FC3975 for ; Sat, 23 Jul 2016 16:11:54 -0400 Received: by mail-pf0-f176.google.com with SMTP id y134so51453063pfg.0 for ; Sat, 23 Jul 2016 13:11:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ghY0PiNgPOmNB6PnsD4YV3l8/11KRa68kfyF6duqDMM=; b=gi5OjJ9GqYr4zWqUrDDzG2BTzxK2ge2FVy3IgTmSa6QUHcXfwnwgEjDgz7PdRljXqZ uEgaM9Kt8TX+KCDFuqPXQorKETyL8D35YfcoS4MXJIzNA9Qu4pUWmSynH44nShnuI0xT LgGy4LEDiadSQ5k4UDlRczKjKBxJGLK+OdYAkUuRJdFTqM/aXxDhIq/dgHvuNtdyExN5 74ZTG6gOjLb3lY3It0jtjBB5cJRQiQqz6RF9BdTw+fK2u+hl7O2/GGb12N5rhEEVOiDe HxIVaLqcZDfgPYclVa+zGmxuRr8lSnGIWQxVt5EeFvwVAudPBKea0DalVEcJIQe8UaVI s0gQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ghY0PiNgPOmNB6PnsD4YV3l8/11KRa68kfyF6duqDMM=; b=VNrvyQ10p9TSmHcDjZY3b6fXUCfZXqppgR2T/PLB0N33/sVkJGHCjxuIfk+5Kg619Z DKsROCH0CWMo0EoWrTDUjoqYJjkaQSqRo7r4H1kT9/1Y3Yg2WHQD5UFol5QFLk8EE9KP pXNA5CeETybSFasxkxaWD1igN12RFm2E37kTh0Pm6CsI3Jmo/tQe+0Q4+PnEtzx4mYDT 1pk9vCpxAmzrnSouM9BiOfvrvJK4uHK8fcXitNziNAc7KmZfNhzs8N/rg3h+08391yVU T2tZqApz1aVMNcNAAI2RlgZhP5DFYs/TBUPzRN6+SIuVAsvboM4FkGlznfoVoI/Mtio5 kWfg== X-Gm-Message-State: AEkoouuOXO9Uy2AKkwYCHZGNenMTAfZu1nJX1rxvKQHGGwUkOA4SkZnsaQcdcy+jAvKwvw== X-Received: by 10.98.26.133 with SMTP id a127mr17050470pfa.46.1469304709403; Sat, 23 Jul 2016 13:11:49 -0700 (PDT) Received: from brians-iphone.att.net (108-201-189-144.lightspeed.sntcca.sbcglobal.net. [108.201.189.144]) by smtp.gmail.com with ESMTPSA id h125sm28973185pfg.54.2016.07.23.13.11.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Jul 2016 13:11:48 -0700 (PDT) To: Yasuo Ohgaki References: <20160721000555.C7F861A810A0@dd1730.kasserver.com> Cc: "internals@lists.php.net" Message-ID: <000a4b48-dffe-93ce-e159-fc1dafe645da@gmail.com> Date: Sat, 23 Jul 2016 13:11:47 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Pipe Operator v2 From: smalyshev@gmail.com (Stanislav Malyshev) Hi! >> $x = loadConfig(); >> $x = buildDic($x); >> $x = getApp($x) >> $x = getRouter($x) >> $x = getDispatcher($x, $request) >> $x = dispatchBusinessLogic($x, $request, new Response()) >> $x = renderResponse($x) >> $x = buildPsr7Response($x) >> $response =emit($x); >> > > I agree the example code is readable, but it makes me feel the > language is a little obsolete. This is a mindset that I feel to be objectionable and take issue with. The idea that we have to constantly invent new syntax to replace working old one, just because old is somehow "obsolete", even though new syntax's only advantage is doing things slightly differently - it seems to me an exactly wrong idea. It may be exciting to invent new syntaxes - but for an industry programmer that has other priorities, like code stability, compatibility, maintainability, etc. "new" is not a positive things unless it gives them measurable or at least perceivable improvement on these qualities. Existing syntax is not "obsolete" and works completely well. New syntax invents new magic variables (thing that never existed in PHP before, adding a whole new conceptual level to PHP mental model) and a new way of doing the same thing that is already perfectly doable right now with exactly the same effort. I personally strongly object to such changes. There is a lot of ways in which PHP needs improvement, but right now I think inventing more syntax tricks in not one of them. Even in syntax department, PHP has areas where we could use improvement (e.g. to name named arguments as one) but this one doesn't seem to do much but doing the same thing in a shiny new way. Read: less comprehensible for people not watching "latest new 20 syntaxes PHP invented in the next version", more things to learn to read PHP code, more things to maintain, more complexity for the language that once was supposed to be accessible to beginners. This is the price of all innovation, but sometimes benefits are much greater and the price is completely warranted. I do not feel this is the case here. -- Stas Malyshev smalyshev@gmail.com