Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129032
Content-Type: multipart/alternative; boundary=Apple-Mail-DD8B4CAE-33CE-4208-96D4-70646E9F5BD3
Content-Transfer-Encoding: 7bit
Precedence: list
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] Fwd: [DISCUSSION] Proposal: Official PHP Language Server (LSP Implementation)
Date: Fri, 31 Oct 2025 13:17:12 -0400
Message-ID: <31718698-00FA-4B73-ACE7-5ECA00636139@benramsey.com>
References: <CAFJFTYb2+mGT-YJZ23qjrQYuuVdqRAv7G16iZhZDMgx6f3NvyQ@mail.gmail.com>
Cc: internals@lists.php.net
In-Reply-To: <CAFJFTYb2+mGT-YJZ23qjrQYuuVdqRAv7G16iZhZDMgx6f3NvyQ@mail.gmail.com>
To: Dan Jessen <danjessen@gmail.com>
From: ben@benramsey.com (Ben Ramsey)


--Apple-Mail-DD8B4CAE-33CE-4208-96D4-70646E9F5BD3
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

> On Oct 31, 2025, at 10:50, Dan Jessen <danjessen@gmail.com> wrote:
>=20
> =EF=BB=BF
> Hello everyone,
>=20
> I=E2=80=99d like to start a discussion about the potential for PHP to have=
 an official Language Server, implementing the Language Server Protocol (LSP=
) =E2=80=94 similar to what other programming languages already provide (e.g=
. Go=E2=80=99s gopls, Elixir=E2=80=99s Expert, etc.).
>=20
> This is not yet a formal RFC, but rather an exploration of whether there=E2=
=80=99s community interest in such a concept, and what form it could take if=
 we agreed it=E2=80=99s worth pursuing.
>=20
> Background / Motivation
> Currently, PHP developers rely on various third-party or editor-specific l=
anguage servers, including Psalm, Intelephense, and phpactor. These tools ar=
e impressive, but they differ in capabilities, maintenance status, and licen=
sing (some are commercial).
> Additionally, several editors (e.g. VS Code, PhpStorm) implement their own=
 non-standardized integrations.
>=20
> By contrast, many modern languages now provide an official language server=
 as part of their toolchain. For example:
> Go: gopls
> Elixir: Expert (official successor to the community-built ElixirLS)
> Rust: rust-analyzer
> TypeScript: TypeScript Server
> These servers improve consistency, tooling integration, and accessibility =E2=
=80=94 independent of any specific IDE or vendor.
>=20
> Why PHP Could Benefit
> Toolchain Completeness
> A programming language should ideally include its own ecosystem of core to=
ols =E2=80=94 including syntax checking, testing, and language intelligence.=

> Editor Independence
> PHP is often associated with PhpStorm because of its strong analysis featu=
res. An official LSP would level the playing field, enabling advanced featur=
es in any editor that supports the protocol.
> Standardization
> A unified and standardized LSP implementation would reduce fragmentation a=
nd improve interoperability across IDEs and plugins.
> Accessibility and Onboarding
> Lowering the barrier for new developers by providing consistent, out-of-th=
e-box editor support.
>=20
> Existing Building Blocks
> The PHP runtime already provides components that could serve as a foundati=
on =E2=80=94 e.g. php -l for syntax checking, reflection APIs, AST via php-a=
st, and insights from static analysis tools like Psalm or PHPStan.
>=20
> This wouldn=E2=80=99t necessarily mean rewriting existing tools, but defin=
ing a common standard =E2=80=94 potentially leveraging or integrating with t=
hose efforts.
>=20
> Next Steps
> I=E2=80=99m not currently in a position to build such a server myself, but=
 I=E2=80=99d like to open a discussion around:
> Whether this aligns with PHP=E2=80=99s roadmap and philosophy.
> Any prior work or discussion on the topic.
> The potential scope =E2=80=94 e.g., core toolchain addition, PECL extensio=
n, or standalone PHP project under the official organization.
> If there=E2=80=99s interest, I=E2=80=99d be happy to draft a more formal R=
FC to outline possible goals, structure, and implementation paths.
>=20
> Thanks for reading =E2=80=94 I=E2=80=99d really appreciate your thoughts, p=
ointers to prior work, or any guidance on how best to take this forward.
>=20
> Best regards,
> Dan

Would such a thing need to be in php-src, or could it be started as a separa=
te code base? IOW, could this be an independent project maintained outside o=
f internals and donated to the PHP project?

Cheers,
Ben


--Apple-Mail-DD8B4CAE-33CE-4208-96D4-70646E9F5BD3
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"><blockquote type=3D"cite">=
On Oct 31, 2025, at 10:50, Dan Jessen &lt;danjessen@gmail.com&gt; wrote:<br>=
<br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<=
div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><div dir=3D=
"ltr">Hello everyone,<br><br>I=E2=80=99d like to start a discussion about th=
e potential for PHP to have an official Language Server, implementing the La=
nguage Server Protocol (LSP) =E2=80=94 similar to what other programming lan=
guages already provide (e.g. Go=E2=80=99s gopls, Elixir=E2=80=99s Expert, et=
c.).<br><br>This is not yet a formal RFC, but rather an exploration of wheth=
er there=E2=80=99s community interest in such a concept, and what form it co=
uld take if we agreed it=E2=80=99s worth pursuing.<br><br><b>Background / Mo=
tivation</b><br>Currently, PHP developers rely on various third-party or edi=
tor-specific language servers, including Psalm, Intelephense, and phpactor. T=
hese tools are impressive, but they differ in capabilities, maintenance stat=
us, and licensing (some are commercial).<br>Additionally, several editors (e=
.g. VS Code, PhpStorm) implement their own non-standardized integrations.<br=
><br>By contrast, many modern languages now provide an official language ser=
ver as part of their toolchain. For example:<br><ul><li>Go: gopls</li><li>El=
ixir: Expert (official successor to the community-built ElixirLS)</li><li>Ru=
st: rust-analyzer</li><li>TypeScript: TypeScript Server</li></ul>These serve=
rs improve consistency, tooling integration, and accessibility =E2=80=94 ind=
ependent of any specific IDE or vendor.<br><br><b>Why PHP Could Benefit</b><=
br><ol><li>Toolchain Completeness<br>A programming language should ideally i=
nclude its own ecosystem of core tools =E2=80=94 including syntax checking, t=
esting, and language intelligence.</li><li>Editor Independence<br>PHP is oft=
en associated with PhpStorm because of its strong analysis features. An offi=
cial LSP would level the playing field, enabling advanced features in any ed=
itor that supports the protocol.</li><li>Standardization<br>A unified and st=
andardized LSP implementation would reduce fragmentation and improve interop=
erability across IDEs and plugins.</li><li>Accessibility and Onboarding<br>L=
owering the barrier for new developers by providing consistent, out-of-the-b=
ox editor support.</li></ol><br><b>Existing Building Blocks</b><br>The PHP r=
untime already provides components that could serve as a foundation =E2=80=94=
 e.g. php -l for syntax checking, reflection APIs, AST via php-ast, and insi=
ghts from static analysis tools like Psalm or PHPStan.<br><br>This wouldn=E2=
=80=99t necessarily mean rewriting existing tools, but defining a common sta=
ndard =E2=80=94 potentially leveraging or integrating with those efforts.<br=
><br><b>Next Steps</b><br>I=E2=80=99m not currently in a position to build s=
uch a server myself, but I=E2=80=99d like to open a discussion around:<br><u=
l><li>Whether this aligns with PHP=E2=80=99s roadmap and philosophy.</li><li=
>Any prior work or discussion on the topic.</li><li>The potential scope =E2=80=
=94 e.g., core toolchain addition, PECL extension, or standalone PHP project=
 under the official organization.</li></ul>If there=E2=80=99s interest, I=E2=
=80=99d be happy to draft a more formal RFC to outline possible goals, struc=
ture, and implementation paths.<br><br>Thanks for reading =E2=80=94 I=E2=80=99=
d really appreciate your thoughts, pointers to prior work, or any guidance o=
n how best to take this forward.<br><br>Best regards,<br>Dan</div>
</div></div>
</div></blockquote><br><div>Would such a thing need to be in php-src, or cou=
ld it be started as a separate code base? IOW, could this be an independent p=
roject maintained outside of internals and donated to the PHP project?</div>=
<div><br></div><div>Cheers,</div><div>Ben</div><div><br></div></body></html>=

--Apple-Mail-DD8B4CAE-33CE-4208-96D4-70646E9F5BD3--