I usually hate this question and threads, because it's a bunch of people arguing that their solution is superior. There are always individuals stating how all they need is VIM or a plain text editor with no syntax highlighting. And then those like myself that feel very productive from the Jetbrains ecosystem because of its superior performance in large codebases and exceptional refactoring tools. No one is going to convince me that I would be more productive learning all the vim hot keys and doing it in a terminal without touching the mouse. It's just not my jam. And I wouldn't try to convince those developers to switch away from vim if they are happy. I prefer the visual feedback that I get from Intellij when refactoring and making really complicated changes. Typing is typing and everything can do that well to some degree with a language plugin. But things like the way my personal choice lays out unit testing and making it easy to retry subsets and see everything I need to see at once works for me. I just don't get the point of these threads that try to narrow in on the "best" ide.
On Sunday, August 20, 2023 at 9:17:35 AM UTC+12 Robert Engels wrote: > Reread what I wrote. Vim with autocomplete, etc is not a simple text > editor with syntax coloring. > > Still every major software engineering org in the world uses an ide (or > multiple). I guess they don’t know what they are doing. > > Btw, Googles current IDE is based on VSCode. > > > On Aug 19, 2023, at 3:24 PM, Jan Mercl <0xj...@gmail.com> wrote: > > > > On Sat, Aug 19, 2023 at 10:06 PM Christian Stewart > > <chri...@aperture.us> wrote: > > > >> Autocomplete and a go language server (gopls) add a ton of speed > because you don't need to look up the docs for function and variable names. > And go to definition improves speed navigating code significantly. > > > > - Using autocomplete and go-to-definiton does not require VSCode or > > any other IDE. > > - I do use autocomplete and go-to-definition. When I said I use no > > IDE, that does not mean I don't use those features. > > - The speed of typing/inputting code is overally a rather negligible > > factor of the total time cost of developing/debugging and maintaining > > any non-toy project. IOW, it's not a significant metric of > > productivity. > > > >> But vim-go can do both, so why not just use it? > > > > Because I use govim? ;-) > > > > (But not for my large projects, gopls chokes on them still too often > > to tolerate it.) > > > > -- > > You received this message because you are subscribed to the Google > Groups "golang-nuts" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to golang-nuts...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/CAA40n-XusymW6gb5OnDa_7QWAWPFSkwKYQMYUm-d7419EZ%2BGkQ%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1e0ef783-83d2-4dbb-a7fb-02cf8786fa15n%40googlegroups.com.
