I would much rather be able to have things like personalised searches (which are identifying).

I might be out by a factor of 2/3 (automatically applied promo deals/credits make it very hard to be sure), but we get 3k messages per month for a seat count of ~60, and finance are concerned about cost.

$2 is probably a good deal for the Extra High 8 minutes of agentic searching/coding/etc when it one-shots a whole project.

$2 is a terrible deal for a 5 second instant retrieval.

I assume you will use your phone for 20-40 years?

LSPs only really pro-actively send diagnostics (error/warning/info/suggest[/code action]).

Everything else is responsive; the client asks for symbols in this document, or completion on this line, etc. And if the client is aware of document changes (which are versioned), it should notify of those before requesting new symbols/etc, but that's not difficult.

I don't know that it's mandatory, but I definitely implemented servers so that they would complete processing changed documents before responding to any later requests.

And if it's just the client re-using cached symbols without asking for an update (which should be very fast if nothing has changed); well, that's foolish.

It was like it only had the basic language support plugin I wrote for myself at uni: basic syntax and current file/directory only source files loaded into context.

So any referenced projects, tooling, even packages in one language, and you have false positive errors everywhere.

And surely redis is a runtime image?

Which is phrased as "not my job" for some reason.

I don't understand why one would go halfway and leave packages which are unneeded for services. The only executable in a hardened container image should be your application.

So never being offered a job because it doesn't exist doesn't lose you anything.

The us is only 5 times bigger

No passenger would accept 30 mins delays every day.