HackerTrans
TopNewTrendsCommentsPastAskShowJobs

alexxys

no profile record

comments

alexxys
·hace 2 años·discuss
I absolutely love autocomplete in VSCode but hate it in Visual Studio while using the same LLM. The big difference for me is the function AcceptNextWord which Visual Studio doesn't have. A long autocomplete suggestion is rarely completely correct and becomes an annoying distraction but one or several words at the beginning of the suggestion are often correct. So, I usually accept only one or few words in VSCode with a hotkey, then type a bit more, then accept few words more etc. That works great for me. Also, I developed intuition in which pieces of code an LLM suggestion would be most probably useless, so I just ignore any suggestions there to avoid unnecessary distraction.

My guess is that many devs who don't like LLM autocomplete, are just unlucky to use a suboptimal UI. As an example, I personally don't understand how some people could like autocomplete in Visual Studio. As you said, it's just too distracting and irritating.

BTW, I use Codeium, not Copilot. But I guess they should have the same autocomplete UI which depends more on IDE than LLM.
alexxys
·hace 2 años·discuss
This meme already exists ;) https://www.reddit.com/r/ChatGPT/comments/128nwi2/bullet_poi...
alexxys
·hace 2 años·discuss
The article talks a lot about async/await but fails to clearly state the main advantage of async code over threads. Async code in general (not only in Rust) allows a server to process thousands of client connections concurrently with minimal latency in a single thread. Even if each client request needs several seconds to process it (assuming the processing is IO-bound). One thread (or more generally, a small number of threads) is much cheaper resource-wise than thousands of threads (in a thread per client scenario).
alexxys
·hace 2 años·discuss
Yeah, RAG can't provide such guarantees. Moreover, even if the correct answer is printed somewhere, LLM+RAG still may produce wrong answer. Example from MS Copilot with GPT-4: https://sl.bing.net/ct6wwRjzkPc It claims that OnePlus 6 has 6.4-inch display, but all linked pages actually claim that it's 6.28. Display resolution and aspect ratio are also wrong in the response.