I agree with the popup argument, but the documentation split you show with "GoDoc" is actually using an LSP, vim-go uses the gopls to provide those functionalities
I cannot stand popups in my editor, including the autocomplete suggestions. I have a simple tab-complete I wrote in my Emacs config that cycles through recently used tokens that would complete what I've already typed, but I can't handle it covering up surrounding code. My main issue with LSPs is that they take something simple and turn it into a distributed system that is buggy and (sometimes) heavy on resource utilization. I used to use VS Code and frequently got popups saying such an such extension had crashed. It was ALMOST ALWAYS something related to parsing responses from the LSP. Why take something simple and make it into something complicated and buggy?
Overengineered imo, why shoudlld we run a full server locally, with all the overhead that entails, just for goto definition etc. Should've just been a ABI interface that compilers implement and editors can call
I agree with the popup argument, but the documentation split you show with "GoDoc" is actually using an LSP, vim-go uses the gopls to provide those functionalities
I cannot stand popups in my editor, including the autocomplete suggestions. I have a simple tab-complete I wrote in my Emacs config that cycles through recently used tokens that would complete what I've already typed, but I can't handle it covering up surrounding code. My main issue with LSPs is that they take something simple and turn it into a distributed system that is buggy and (sometimes) heavy on resource utilization. I used to use VS Code and frequently got popups saying such an such extension had crashed. It was ALMOST ALWAYS something related to parsing responses from the LSP. Why take something simple and make it into something complicated and buggy?
distracting and bug ridden. The muscle memory argument is great.
Overengineered imo, why shoudlld we run a full server locally, with all the overhead that entails, just for goto definition etc. Should've just been a ABI interface that compilers implement and editors can call