question: Do you have info on the philosophy of using dotnet-suggest

My motivation for looking at command-line-api was that my javascript library took 0.2 seconds or so to do completions even when it was a fixed small list. Seemed to be related to node launch time.

My test prototype dotnet app returned completions in 0.02 seconds or less. I perceived them to be as quick as the completions for `git` which are super fast.

So I convinced myself that I was relying on completions enough with my app that I should switch to dotnet so I'd get lightning fast completions.

But relying on dotnet-suggest seems to make things much slower than my node app.

Curious what the motivation was. I know one obvious reason is so that you can have one shim file for all dotnet tools. Are there other goals as well? Perhaps the performance issues I'm seeing are related to the fact that I'm not really seeing completions work reliably. So there may be another factor in play on my box.

I see you are measuring performance so it's obviously important. Is it "fast" normally? I use `git` as my base line. It always seems "instantaneous".