Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80078 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3240 invoked from network); 2 Jan 2015 00:53:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Jan 2015 00:53:06 -0000 Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.25 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.25 out1-smtp.messagingengine.com Received: from [66.111.4.25] ([66.111.4.25:42640] helo=out1-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DC/14-18015-FEBE5A45 for ; Thu, 01 Jan 2015 19:53:04 -0500 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 80C3820744 for ; Thu, 1 Jan 2015 19:53:01 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Thu, 01 Jan 2015 19:53:01 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:message-id:date:from :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=nMziBJaWZJOpkP8FTpoDol 0gTIg=; b=jr4BykEpfKO+zdExnFredjKw/jAU9uks+MU46MrXye3AdtgS+JBe+U miFPgdGUfLsvQYr9urPQnVvo/FBXFpmRPSKrEvOLI1BExPo4x0AG5r0O71oBug/c VlAoyh0r6NB8GHpQxHH+yBhMNWUq0RPnOIrYxlx126I/Y33PMGUrE= X-Sasl-enc: v9tKb8WtdZfgQlGNzEHfPVjYXKX/Q5EFCTdf2/Hp3yuj 1420159981 Received: from [192.168.42.123] (unknown [98.226.241.18]) by mail.messagingengine.com (Postfix) with ESMTPA id 36A46C00281 for ; Thu, 1 Jan 2015 19:53:01 -0500 (EST) Message-ID: <54A5EBEC.9060204@garfieldtech.com> Date: Thu, 01 Jan 2015 18:53:00 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: internals@lists.php.net References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me> <54A5051F.1090400@php.net> <54A52AE6.70704@fischer.name> <54A56EB3.2000308@fischer.name> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints From: larry@garfieldtech.com (Larry Garfield) On 01/01/2015 10:35 AM, Andrea Faulds wrote: >> Now, going on step back here (talking about me), I'm speaking up because >>> my< needs are developer are different (mostly speaking about backend >> code, interfaces, libraries, frameworks) but OTOH I'm not a big known >> open source framework developer either ;) >> >> I would honestly be interested what the big framework/library players >> actually want/need; do they prefer this implicit scalar type conversion >> system or rather have a rigid system like the current object types but >> for scalars too? I think decision on this RFC should include also >> "their" saying too. >> >> It's complex because we can't force anyone to participate but I think >> above all these are the most important audience here because they know >> what they want and they know what their users want. I say this because >> usage of object types in PHP is almost non-existent (or, there are just >> too few cases) compared to the architecture of some of the >> framework/library systems out there. > That’s a fair point. I’m not sure how they feel about it. > > Their views aren’t necessarily the most important, though. Frameworks can do whatever they like, but what ultimately matters is what’s best for the end users, who don’t deal with the framework internals. > > Thanks. > -- > Andrea Faulds > http://ajf.me/ The "end users" of php-src are "people who write PHP code". Those are the end users that we should be concerned with. "People who visit web sites" are *their* end users. Those people don't care in the slightest what happens on this list; they care that the people writing PHP code can do their job in a minimum amount of time and with a minimum amount of bugs. So asking developers of the major PHP frameworks and applications what would help them do their job in a minimum amount of time with a minimum amount of bugs is absolutely a worthwhile endeavor to figure out what would be "best". "User research" in this case, means talking to the lead developers of Zend Framework, Symfony, Drupal, Wordpress, phpBB, and so on. I'd be happy to make introduction for you on the FIG mailing list, which is the best collection of such people I know of. --Larry Garfield