Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129036
Precedence: list
MIME-Version: 1.0
References: <CAFJFTYZK+FD+02YXmW9NuNoOfepyZYVZTWDJVSD18rodHfnZDQ@mail.gmail.com>
 <CAFJFTYb2+mGT-YJZ23qjrQYuuVdqRAv7G16iZhZDMgx6f3NvyQ@mail.gmail.com>
In-Reply-To: <CAFJFTYb2+mGT-YJZ23qjrQYuuVdqRAv7G16iZhZDMgx6f3NvyQ@mail.gmail.com>
Date: Fri, 31 Oct 2025 17:44:56 -0600
Message-ID: <CA+JpajkEaOKtr3bA-NG0ytTg2uDiKzx7eTd2yafQph4YtUJbWw@mail.gmail.com>
Subject: Re: [PHP-DEV] Fwd: [DISCUSSION] Proposal: Official PHP Language
 Server (LSP Implementation)
To: Dan Jessen <danjessen@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009013ce06427cf4b2"
From: hamiegold@gmail.com (Hammed Ajao)

--0000000000009013ce06427cf4b2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 31, 2025, 8:48=E2=80=AFa.m. Dan Jessen <danjessen@gmail.com> wr=
ote:

> Hello everyone,
>
> I=E2=80=99d like to start a discussion about the potential for PHP to hav=
e 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.).
>
> 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.
>
> *Background / Motivation*
> Currently, PHP developers rely on various third-party or editor-specific
> language servers, including Psalm, Intelephense, and phpactor. These tool=
s
> are impressive, but they differ in capabilities, maintenance status, and
> licensing (some are commercial).
> Additionally, several editors (e.g. VS Code, PhpStorm) implement their ow=
n
> non-standardized integrations.
>
> By contrast, many modern languages now provide an official language serve=
r
> 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.
>
> *Why PHP Could Benefit*
>
>    1. Toolchain Completeness
>    A programming language should ideally include its own ecosystem of
>    core tools =E2=80=94 including syntax checking, testing, and language =
intelligence.
>    2. Editor Independence
>    PHP is often associated with PhpStorm because of its strong analysis
>    features. An official LSP would level the playing field, enabling adva=
nced
>    features in any editor that supports the protocol.
>    3. Standardization
>    A unified and standardized LSP implementation would reduce
>    fragmentation and improve interoperability across IDEs and plugins.
>    4. Accessibility and Onboarding
>    Lowering the barrier for new developers by providing consistent,
>    out-of-the-box editor support.
>
>
> *Existing Building Blocks*
> The PHP runtime already provides components that could serve as a
> foundation =E2=80=94 e.g. php -l for syntax checking, reflection APIs, AS=
T via
> php-ast, and insights from static analysis tools like Psalm or PHPStan.
>
> This wouldn=E2=80=99t necessarily mean rewriting existing tools, but defi=
ning a
> common standard =E2=80=94 potentially leveraging or integrating with thos=
e efforts.
>
> *Next Steps*
> I=E2=80=99m not currently in a position to build such a server myself, bu=
t 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 ex=
tension,
>    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 =
RFC to outline
> possible goals, structure, and implementation paths.
>
> Thanks for reading =E2=80=94 I=E2=80=99d really appreciate your thoughts,=
 pointers to
> prior work, or any guidance on how best to take this forward.
>
> Best regards,
> Dan
>


I actually had a similar idea like 2 years ago and started working on a
golang port of nikics parser. Its still a side project and not yet well
documented, but it works and its significantly faster.

I can make it presentable and publish it this weekend if theres any
interest in going this route

Cheers,
Hammed.

>

--0000000000009013ce06427cf4b2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><br><br><br><div class=3D"gmail_quote gmail_quote_contain=
er" dir=3D"auto"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 31, 2025=
, 8:48=E2=80=AFa.m. Dan Jessen &lt;<a href=3D"mailto:danjessen@gmail.com">d=
anjessen@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">Hello everyone,=
<br><br>I=E2=80=99d like to start a discussion about the potential for PHP =
to have an official Language Server, implementing the Language Server Proto=
col (LSP) =E2=80=94 similar to what other programming languages already pro=
vide (e.g. Go=E2=80=99s gopls, Elixir=E2=80=99s Expert, etc.).<br><br>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 w=
e agreed it=E2=80=99s worth pursuing.<br><br><b>Background / Motivation</b>=
<br>Currently, PHP developers rely on various third-party or editor-specifi=
c language servers, including Psalm, Intelephense, and phpactor. These tool=
s are impressive, but they differ in capabilities, maintenance status, and =
licensing (some are commercial).<br>Additionally, several editors (e.g. VS =
Code, PhpStorm) implement their own non-standardized integrations.<br><br>B=
y contrast, many modern languages now provide an official language server a=
s part of their toolchain. For example:<br><ul><li>Go: gopls</li><li>Elixir=
: Expert (official successor to the community-built ElixirLS)</li><li>Rust:=
 rust-analyzer</li><li>TypeScript: TypeScript Server</li></ul>These servers=
 improve consistency, tooling integration, and accessibility =E2=80=94 inde=
pendent 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 =
include its own ecosystem of core tools =E2=80=94 including syntax checking=
, testing, and language intelligence.</li><li>Editor Independence<br>PHP is=
 often associated with PhpStorm because of its strong analysis features. An=
 official LSP would level the playing field, enabling advanced features in =
any editor that supports the protocol.</li><li>Standardization<br>A unified=
 and standardized LSP implementation would reduce fragmentation and improve=
 interoperability across IDEs and plugins.</li><li>Accessibility and Onboar=
ding<br>Lowering the barrier for new developers by providing consistent, ou=
t-of-the-box editor support.</li></ol><br><b>Existing Building Blocks</b><b=
r>The PHP runtime already provides components that could serve as a foundat=
ion =E2=80=94 e.g. php -l for syntax checking, reflection APIs, AST via php=
-ast, and insights from static analysis tools like Psalm or PHPStan.<br><br=
>This wouldn=E2=80=99t necessarily mean rewriting existing tools, but defin=
ing a common standard =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 p=
osition to build such a server myself, but I=E2=80=99d like to open a discu=
ssion around:<br><ul><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, o=
r 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 out=
line possible goals, structure, and implementation paths.<br><br>Thanks for=
 reading =E2=80=94 I=E2=80=99d really appreciate your thoughts, pointers to=
 prior work, or any guidance on how best to take this forward.<br><br>Best =
regards,<br>Dan</div></div></div></blockquote></div><div dir=3D"auto"><br><=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">I actually had a similar=
 idea like 2 years ago and started working on a golang port of nikics parse=
r. Its still a side project and not yet well documented, but it works and i=
ts significantly faster.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D=
"auto">I can make it presentable and publish it this weekend if theres any =
interest in going this route</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">Cheers,=C2=A0</div><div dir=3D"auto">Hammed.</div><div class=3D"gmail_=
quote gmail_quote_container" dir=3D"auto"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv dir=3D"ltr"><div class=3D"gmail_quote">
</div></div>
</blockquote></div></div>

--0000000000009013ce06427cf4b2--