OK, thanks again, if it's complex don't worry about it, as Russ said it's easy to mentally mix some of those terms. I really apreciate your work and I think this survey gives some interesting insights about the Go community.
On Mon, Mar 6, 2017 at 9:25 PM, Russ Cox <r...@golang.org> wrote: > On Mon, Mar 6, 2017 at 12:42 PM, Pablo de la Concepción Sanz < > pconcepc...@gmail.com> wrote: > >> Hi, >> >> First of all, thanks for collecting and sharing the info. I've noticed >> that on some questios, some answers are mostly the same but they are >> separate. For instance for "What one addition would make the biggest >> improvement to Go editing in your preferred editor?" The two top ones are >> "debugging" and "debugger", that to my mind should be the same. >> >> Is there a reason to separate those cases? >> > > Those tables are generated programmatically according to the algorithm > described in the "reading the data" section after the first such display. > If you want to mentally add debugging and debugger together, sure, go > ahead. But as Steve said the goal in those plots was to show the actual > data, not our interpretation of the data. Our take on the data is in the > main text instead. > > And of course, in this specific case, there are many topics related to > debugging that don't have to do with debuggers. > > Russ > -- 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. For more options, visit https://groups.google.com/d/optout.
