Re: Zephir, and other tangents

From: Date: Mon, 23 Sep 2024 17:07:59 +0000
Subject: Re: Zephir, and other tangents
References: 1 2 3 4 5 6 7 8 9 10 11 12  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On Mon, Sep 23, 2024 at 8:14=E2=80=AFAM Mike Schinkel <[email protected]>=
 wrote:
> > At which point, some managed hosting servers might be more willing to i=
nstall it. Not the ones who don't even install ext/curl, those are never go=
ing to benefit from this.
> There are very few (if any) that won't install curl as you cannot run Wor=
dPress w/o curl.  Your knowledge of what hosting providers will and will no=
t install seems to be rather dated.

Just to add to that: without curl, WordPress falls back to a limited
fsockopen-based network transport. Sometimes that's problematic, so
I'm incubating a dependency-free HTTP client that can do streaming,
async connections etc. using only functions shipped in core PHP [1].
I'll eventually propose it for WordPress core as either a better
fallback or as a replacement for curl. If PHP had WASM support,
WordPress could ship curl.wasm as a fallback and focus on the product
more than on the plumbing.

> BTW, Dennis, could you see WordPress recommending a WASM extension if PHP=
 bundled one here? https://make.wordpress.org/hosting/handbook/server-envir=
onment/#php-extensions

I'm not Dennis, but I think that's very real. If PHP had a solid,
official, viable WASM extension today, I'd already have a PR proposing
shipping WASM binaries with WordPress core. I'd also be advocating
everywhere to officially include the WASM PHP extension on the list of
WordPress-recommended extensions. And if that extension was a part of
every PHP build, I'd be advocating to list it as a requirement.

[1] https://github.com/WordPress/blueprints-library/blob/trunk/src/WordPres=
s/AsyncHttp/Client.php

- Adam


Thread (43 messages)

« previous php.internals (#125655) next »