|Re: [ide-dev] Auto content assist|
On 04/24/2017 05:05 PM, Daniel Megert wrote:
Content assist must return results quickly. It's not like an action where you expect to get results later.Compare it with other IDEs who have asynchronous edition of Java, see how fast/slow they can be (sometimes completion can take long time in VSCode) and chat with the users about which approach they like better.
Users are ready to wait some time (a few seconds even) and they've been used to it since the inception of Ajax applications who made asynchronous and slow performance mainstream. Nowadays, to avoid irritating users in an editor, asynchronous/non-blocking is the must-have, good performances is the nice-to-have.
I suggest you give a try to some of the editors in Eclipse IDE provided on top of the LSP4E. Completion is often slower than JDT, but as UI is not blocked in the meantime, it still seems fluent - and you never get completion proposals removed because they're slow to compute.