> On Nov 1, 2025, at 14:38, Dan Jessen <[email protected]> wrote: > > > Thanks Marco — I agree that any official LSP should follow the PHP spec > closely and avoid adding new type semantics. > > The issue isn’t the lack of servers, but fragmentation. Psalm and Phpactor > differ in scope and design, while Phan’s LSP docs haven’t been updated in > years and its Vim plugin is around seven years old. None are standardized or > maintained alongside PHP itself. > > PhpStorm is an excellent IDE, but it’s premium — and the fact it’s the only > consistently recommended option highlights a tooling gap. Developers using VS > Code, Neovim, Emacs, or Sublime Text often get a very different experience. > > The Language Server Protocol exists to solve exactly this: as Tom Djenius de > Vries put it, it turns the M×N problem (M editors × N languages) into M+N — > each only needs one integration point. > > A spec-aligned, officially maintained PHP LSP could unify that baseline and > 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 VS Code extensions, since all of these projects have an interest in a spec-aligned PHP LSP. Perhaps PHP-FIG could be a good host for this working group? Cheers, Ben
