4 ms·
It's important to note that here the client server architecture is asynchronous and multiple. This allows it to actually decouple slow interactions as auto-comp
by legulere 10y ago
It's important to note that here the client server architecture is asynchronous and multiple.
This allows it to actually decouple slow interactions as auto-completion from things that need low latency such as typing.
You actually see this in many IDEs that more features make editing feel more sluggish. This shouldn't happen with this structure.
- thomasahle 10y agoIs auto completion really useful, if it's a lot slower than the rest of the program? Maybe if a part is too slow, you should either optimize it or get rid of it?
- oblio 10y agoWell, considering that as far as developer tools are concerned many of the best sellers are IDEs with Intellisense (intelligent code completion, based on syntax and semantics)...
- viraptor 10y agoSometimes you want the autocompletion, sometimes you don't. You can do it in synchronous style, where you have 2 choices: a) delay the typing when the user doesn't care about the autocomp, b) require an extra action to activate autocomp when the user wants it. You can also do it async style and have neither of the drawbacks - if the user types too quickly, the autocomp just doesn't show up.
- flukus 10y ago> It's important to note that here the client server architecture is asynchronous and multiple. Both can (and have) been achieved without a client server architecture.