I suspect there's an analogy of blub programming languages for IDEs. Once you've seen more powerful solutions you miss them in less capable tools. If you haven't learnt them, you're indifferent.
This is probably why 'table stakes for a modern IDE' viewpoints vary so much.
miniblog.
Related Posts
The author of rust-analyzer discussing how language features help or hinder fast IDEs.
If you allow `from m import *` you can't analyse files in isolation, and it's even harder in Rust.
Really thoughtful critique of the Language Server Protocol, what IDEs need to express, and the design decisions made.
Writing a parser that is resilient to syntax errors, and why a parser should always return something: https://duriansoftware.com/joe/constructing-human-grade-parsers
(The latter property is important in e.g. IDEs and it's rarely discussed!)