3 ms·

The initial question was "Is there really a sizeable number of devs who don't intend to ever rely on Copilot?", not "Are all Vim users who type fast anti-Copilo

The initial question was "Is there really a sizeable number of devs who don't intend to ever rely on Copilot?", not "Are all Vim users who type fast anti-Copilot?". I don't mean to dismiss your data point, just to put things in context. Since Copilot is generally recognized as a useful tool, there will of course be Vim users with great typing speed who still find it useful regardless. Now, when it comes to Go, I find that there isn't much repetitive code to write (especially since generics landed in Go 1.18). Some people say that error handling is repetitive, but I find that those people just bubble up errors without adding appropriate context, which makes them less useful. But I haven't personally found a scenario in which I explicitly thought "damn, I know exactly what I need to write, but it's so long - I wish someone would write it for me".

radlad 3y ago
And yet the comment I'm replying to didn't say "I won't ever rely on Copilot," it said "I can say with confidence that Copilot isn't that useful to me." I made my comment because I hope others who are fast typists, and familiar with their tools, do give Copilot a try. I expected to hate it, didn't try it for a long time, and was quite surprised when I did. > But I haven't personally found a scenario in which I explicitly thought "damn, I know exactly what I need to write, but it's so long - I wish someone would write it for me". Test case setup comes to mind. Another place it's useful is for writing long function-interface signatures. Or adding a bunch of similar "case" statements to a switch. Generics still have a ton of limitations.