Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:123011 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 8387B1A009C for ; Sun, 7 Apr 2024 10:44:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1712486712; bh=TlgLOtylJrW0yoqrrsx8VCTlNmrQQUv9nE15eswoBeE=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=dpl5A9p+h/RVd3aQA63BGY8kYMInDP9x78CK1pBYSlJv4c/wm0W21yk0ecFTOfb2n hF/CCPVu0cDZT1t6fe5OF6byv0G7YEeNnZL8B3zyRNUdmU7FE3FZV5vCmcYmEXctyH 7JN7hxwQrmr412XmnpvhdynVNqBONklB6SlR+6EQOwDr43JK3q3d+tfLi5/jyNQi65 S495+O6efGryNtk8AyRWE+A58wdUrjBURTXiSMAE6+O8xWrHHXPl6or2ETsVme0t68 JdLPpGczRHdDEjag4K071hO7ttvsKIGtVnDdtuQjQG8idXOTh7iDYf4bPYTpk6i10j fM2I8DP3pMSfg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 98114180074 for ; Sun, 7 Apr 2024 10:45:10 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail.sakiot.com (mail.sakiot.com [160.16.227.216]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 7 Apr 2024 10:45:10 +0000 (UTC) Received: from smtpclient.apple (62.152.159.133.rev.vmobile.jp [133.159.152.62]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mail.sakiot.com (Postfix) with ESMTPSA id 022BE401F4; Sun, 7 Apr 2024 19:44:36 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com; s=default; t=1712486676; bh=TlgLOtylJrW0yoqrrsx8VCTlNmrQQUv9nE15eswoBeE=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=R/FecTyfe3urrWv3Yrr2OFoBtTalKqvRwITRnDo2BSuGLKy0vmw1Te5QLefFM47FS W2pL16lHhPPyzB4oTCv3VBDnBscArg+93Yhg0K0Pu9nfqJgdcbR/jmhuyQdaup5Pry L5CsjodU0mkxjeTnub9MBAZgKrvcxiK7EyIbLymE= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net Mime-Version: 1.0 (1.0) Subject: Re: [PHP-DEV] Native decimal scalar support and object types in BcMath - do we want both? Date: Sun, 7 Apr 2024 19:44:22 +0900 Message-ID: References: <240D79D1-708D-45A7-9989-D28893955D6E@rwec.co.uk> Cc: internals@lists.php.net In-Reply-To: <240D79D1-708D-45A7-9989-D28893955D6E@rwec.co.uk> To: "Rowan Tommins [IMSoP]" X-Mailer: iPhone Mail (21D61) From: saki@sakiot.com (Saki Takamachi) Hi Rowan, >> On 7 April 2024 01:32:29 BST, Jordan LeDoux wro= te: >>=20 >> Internals is just volunteers. The people working on BCMath are doing that= >> because they want to, the people working on scalar decimal stuff are doin= g >> that because they want to, and there's no project planning to tell one >> group to stop. That's not how internals works (to the extent it works). >=20 > I kind of disagree. You're absolutely right the detailed effort is almost a= lways put in by people working on things that interest them, and I want to m= ake clear up front that I'm extremely grateful to the amount of effort peopl= e do volunteer, given how few are paid to work on any of this. >=20 > However, the goal of the Internals community as a whole is to choose what c= hanges to make to a language which is used by millions of people. That absol= utely involves project planning, because there isn't a marketplace of PHP fo= rks with different competing features, and once a feature is added it's very= hard to remove it or change its design. >=20 > If - and I stress I'm not saying this is true - IF these two features have= such an overlap that we would only want to release one, then we shouldn't j= ust accept whichever is ready first, we should choose which is the better so= lution overall. And if that was the case, why would we wait for a polished i= mplementation of both, then tell one group of volunteers that all their hard= work had been a waste of time? >=20 > So I think the question is very valid: do these two features have distinct= use cases, such that even if we had one, we would still want to spend time o= n the other? Or, should we decide a strategy for both groups to work togethe= r towards a single goal? >=20 > That's not about "telling one group to stop", it's about working together f= or the benefit of both users and the people volunteering their effort, to wh= om I am extremely grateful. >=20 > Regards, > Rowan Tommins > [IMSoP] I don't think the two threads can be combined because they have different go= als. If one side of the argument was, "How about to add BCMath?" then perhap= s we should merge the discussion. But BCMath already exists and the agenda i= s to add an OOP API. In other words, one is about adding new features, and the other is about imp= roving existing features. I agree that it would be wise to merge issues that can be merged. Regards. Saki=