Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:127314 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 lists.php.net (Postfix) with ESMTPS id 897D81A00BC for ; Wed, 7 May 2025 22:02:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1746655233; bh=YSZMVT3cFwBwrpaNMsLmEQ6u0h91cgD5tuOEKdwyB7k=; h=Date:To:From:Cc:Subject:In-Reply-To:References:From; b=Pbo3DullERMTvCSPyqb+gAeO7Q3H7OQGdIWFzdpnts4L0mgHKwXVuaCV5OsgkUBPM ZvQQFw+DfN18f54oFGzgaWCcJImpSXb/w+sVW6eA5tgVg267iuobvlLyX75lYCDiZ1 0ikyUhZiLyFK7GlXVSJncje8QDOwJ1VMs+MFo3ZbPF2E/Fd8VyDnyRubU8yt3fXIGO zRmftczd2zXHQr9TI+urzs1Ypot8yx2OTXO1+uomRa5uBCis5Z8vs8hJ//ZXZuERQZ D2nXtvuHH4tX4fiDIV3dT1Sj2Yn16uCYZNtJB/qDeh+256w3cC0vjZdfFlvQ8i/R9g WXqvBbkOTvWcQ== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D3C1A18007C for ; Wed, 7 May 2025 22:00:31 +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,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from mail-4317.protonmail.ch (mail-4317.protonmail.ch [185.70.43.17]) (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 ; Wed, 7 May 2025 22:00:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gpb.moe; s=protonmail3; t=1746655363; x=1746914563; bh=YSZMVT3cFwBwrpaNMsLmEQ6u0h91cgD5tuOEKdwyB7k=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=6ZKacL7uTWv541R2Va/lbixbS/oMlHKTr5oOkhFl2jMR+Nps3Ght4dMacSO82qhAI L/ibbjPGjEt3/rZ42wCRi9X9ddaKb5HEaYmonoM3sxdEnczt4rjqAnCkwXWZMeeh3q leW4V38iAeAgrj6wBg/s63WiRKNmtzG/ViGNvGOTW542/tMExRvBGo6dkohqrCGw8n sSJQs7UDPei3n0NHeSujcdVD+xMsWiQyhBXLqiK2pJsqxV9eAEsjukgNATs2hp2I9+ jIpt1Lkkwed1lHHZsNp9u/bD9tSDMmmf6/fKRQWv4aI/cR4zu2WXXOA6NCzYvTlYoy F45y3Ak8DFEvA== Date: Wed, 07 May 2025 22:02:37 +0000 To: "Paul M. Jones" Cc: =?utf-8?Q?M=C3=A1t=C3=A9_Kocsis?= , PHP Internals List Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API Message-ID: In-Reply-To: References: Feedback-ID: 96993444:user:proton X-Pm-Message-ID: 9f947002912a8f53ade9a82ee29a429631e85ecb Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: internals@gpb.moe ("Gina P. Banyard") On Wednesday, 7 May 2025 at 20:20, Paul M. Jones wrote= : > Hi Mat=C3=A9 and all, >=20 > > On May 5, 2025, at 16:36, M=C3=A1t=C3=A9 Kocsis kocsismate90@gmail.com = wrote: > >=20 > > Hello Internals, > >=20 > > After more than a hundred emails refining even the tiniest details, we = have reached a point where I'd like to call for a vote. > > I know that the new API still doesn't support many use-cases, it still = has missing pieces, but now it includes a cohesive set > > of functionality that could be a very useful basic building block for m= ost people. > >=20 > > That said, I don't intend to change anything about the RFC anymore, unl= ess there's still some factual error in it. There are a lot of > > possibilities how such a large API can look like, and this RFC approach= es the problem the way it is currently described, > > and not in any other way. > >=20 > > So unless some very serious issues arise, I'm going to start the vote o= n 8th May, possibly in the morning (according to UTC). >=20 >=20 > I am on record as wanting very much to see some decent web-centric object= s in core PHP (Request, Response, Uri/Url, etc). >=20 > To my chagrin, despite the fact that its goals are laudable, I do not thi= nk this RFC is in a ready state to provide such objects. > [...] >=20 > -- pmj Considering that this RFC was in discussion for over 10 months, and you only started providing input 2 months ago after there have already = been serious alterations to it _twice_. I am not sure your "rant" is something that is at all productive. You are free to vote against it, but stalling the work someone has committe= d just because you don't think it is ready is not how any of this works. Looking from the sidelines, you seem to have the opinion that we should be = standardizing existing userland design. This is not what you want, because if you do this you get POSIX, and POSIX = is notoriously inconsistent and kinda bad. And maybe this is what FIG did, which whatever, but core is not FIG nor use= rland. So let's go through your points: > - is too broad in scope; An RFC author is allowed to choose whatever scope they want. > - acknowledges it is incomplete, with work left undone; Using multiple RFCs to provide incremental improvements to the language is = a standard thing we do. Therefore, this point is moot. > - admits to standards non-compliance; and, Non-compliance with what? WHATWG which is a living standard? Not having one component of the WHATWG spec? The same way, the new 8.4 DOM classes don't implement the whole living DOM = spec? > - has an uncertain API. Frankly, 90% of the recent uncertainty has seemingly come from you trying t= o "rework" the RFC to your own taste. If you think this should first be an extension or a userland package then f= eel free to do it, regardless of the result of this vote. Considering that one of the main maintainers of an actual popular userland = URI library has actively been participating in the discussions since the be= ginning and help shape this RFC, makes me believe this is very much ready to vote, compared to the opinion o= f someone that is trying to chime in last minute. Sincerely, Gina P. Banyard