Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129050
Content-Type: multipart/alternative; boundary=Apple-Mail-30AE6F66-0BA6-493B-8C7D-5BCA4A3EDC22
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: Sat, 1 Nov 2025 18:35:16 -0500
Message-ID: <717A650A-EA7C-4733-A301-31E2E5402D66@benramsey.com>
References: <CAFJFTYYnzV3qOGJunaGhHTX3-nSBLMUUyddA1Rgt2F4Z4EFskw@mail.gmail.com>
In-Reply-To: <CAFJFTYYnzV3qOGJunaGhHTX3-nSBLMUUyddA1Rgt2F4Z4EFskw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
From: ben@benramsey.com (Ben Ramsey)


--Apple-Mail-30AE6F66-0BA6-493B-8C7D-5BCA4A3EDC22
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

> On Nov 1, 2025, at 14:38, Dan Jessen <danjessen@gmail.com> wrote:
>=20
> =EF=BB=BF
> Thanks Marco =E2=80=94 I agree that any official LSP should follow the PHP=
 spec closely and avoid adding new type semantics.
>=20
> The issue isn=E2=80=99t the lack of servers, but fragmentation. Psalm and P=
hpactor differ in scope and design, while Phan=E2=80=99s LSP docs haven=E2=80=
=99t been updated in years and its Vim plugin is around seven years old. Non=
e are standardized or maintained alongside PHP itself.
>=20
> PhpStorm is an excellent IDE, but it=E2=80=99s premium =E2=80=94 and the f=
act it=E2=80=99s the only consistently recommended option highlights a tooli=
ng gap. Developers using VS Code, Neovim, Emacs, or Sublime Text often get a=
 very different experience.
>=20
> The Language Server Protocol exists to solve exactly this: as Tom Djenius d=
e Vries put it, it turns the M=C3=97N problem (M editors =C3=97 N languages)=
 into M+N =E2=80=94 each only needs one integration point.
>=20
> A spec-aligned, officially maintained PHP LSP could unify that baseline an=
d make PHP development more consistent and accessible across editors.

IMO, this is something that would work best as a working group involving the=
 maintainers of PHPStan, Psalm, PHP CodeSniffer, PhpStorm, and the related V=
S Code extensions, since all of these projects have an interest in a spec-al=
igned PHP LSP. Perhaps PHP-FIG could be a good host for this working group?

Cheers,
Ben


--Apple-Mail-30AE6F66-0BA6-493B-8C7D-5BCA4A3EDC22
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 Nov 1, 2025, at 14:38, Dan Jessen &lt;danjessen@gmail.com&gt; wrote:<br><=
br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<d=
iv dir=3D"auto"><div dir=3D"auto">Thanks Marco =E2=80=94 I agree that any of=
ficial LSP should follow the PHP spec closely and avoid adding new type sema=
ntics.</div><div dir=3D"auto"><br></div><div dir=3D"auto">The issue isn=E2=80=
=99t the lack of servers, but fragmentation. Psalm and Phpactor differ in sc=
ope and design, while Phan=E2=80=99s LSP docs haven=E2=80=99t been updated i=
n years and its Vim plugin is around seven years old. None are standardized o=
r maintained alongside PHP itself.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">PhpStorm is an excellent IDE, but it=E2=80=99s premium =E2=80=94 a=
nd the fact it=E2=80=99s the only consistently recommended option highlights=
 a tooling gap. Developers using VS Code, Neovim, Emacs, or Sublime Text oft=
en get a very different experience.</div><div dir=3D"auto"><br></div><div di=
r=3D"auto">The Language Server Protocol exists to solve exactly this: as Tom=
 Djenius de Vries put it, it turns the M=C3=97N problem (M editors =C3=97 N l=
anguages) into M+N =E2=80=94 each only needs one integration point.</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">A spec-aligned, officially mainta=
ined PHP LSP could unify that baseline and make PHP development more consist=
ent and accessible across editors.</div></div><div class=3D"gmail_quote gmai=
l_quote_container"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div>
</div></blockquote><br><div>IMO, this is something that would work best as a=
 working group involving the maintainers of PHPStan, Psalm, PHP CodeSniffer,=
 PhpStorm, and the related VS Code extensions, since all of these projects h=
ave an interest in a spec-aligned PHP LSP. Perhaps PHP-FIG could be a good h=
ost for this working group?</div><div><br></div><div>Cheers,</div><div>Ben</=
div><div><br></div></body></html>=

--Apple-Mail-30AE6F66-0BA6-493B-8C7D-5BCA4A3EDC22--