@suede__
I like the joke that they wrote Go while waiting for their C to compile.
@Wako_san91
"You done messed up Balake!" we're never calling anyone Blake ever again 😂
@The1RandomFool
From now on, when I need the length of any array-like object, I'll just call it nn. What a good variable name!
@FrankHarwald
1:00 As a dev who's comping from the engineering math side of things who has seen a lot of fortran and c code that looks like it's coming from a physics or analysis math book, I disagree that single letter variables are always a bad thing - especially when each of them are confined to clear local scopes & you happen to have to deal with a lot of them at the same time. if you don't know: using single letter names in math, physics & engineering for local or bounded scoped variables, constants or expression is not just a decades centuries old way of writing things, it's also more readable when you get more complicated expression. But granted, the stuff that this go-programmer wrote isn't anywhere near that kind of complexity (nor are most things programmers write).
@Omnifarious0
22:50 - I kind of agree that threads are not really the best model for concurrency. They're pretty hard to reason about.
@lazyplayer1
Booo only real language is MS PowerPoint
@suede__
I have done golang at my job for about 5 years, and the convention of one letter variables is horrible. It's a compiled language. Give it some actual names. The only place I do it is the receiver variable because it's the same across every function.
@Bolpat
21:20 The issue of the CC-by license of the Go mascot is that sharing it without attribution is copyright infringement. The CC0 license is ideal for something like that. Ferris, the unofficial Rust mascot is under CC0.
@user-hk3ej4hk7m
the lsp being to a similar level to copilot probably means most of your characters are boilerplate.
@alfiegordon9013
Single letter variables as a convention is weird to me given that 90% of the go team came from the Plan 9 group at bell labs, and the source for Plan 9 is incredibly readable even for someone like me who know very little in terms of its library and dialect of C
@maxmouse3
6:05 absolutely 100% agree. Best creations come out of inconveniences and annoyances
@herroic
Go being 14 years old is crazy
@Ic37r011
I agree with that. The variables with one letter are more difficult to read for the developer. Not following the rule of clarity from Unix Philosophy.
@bloom945
6:36 cheese lovers be like
@vainoleppanen8971
1:45 I agree with Pike and Kernighan: "Use descriptive names for globals, short names for locals" (The practice of programming, 1999). If the entire function is 2-3 lines long, I can tolerate one character parameters, but a full single word is usually better. There's exceptions. E.g. "n" is often used very consistently in some standard functions but IMO most programmers wouldn't get the convention if you just use it as a variable; it's not that hard to use "pLengh" in "WriteString" function (2:14). And "i" is standard: no one should challenge it's use if there's no inner similar loop.
@nyahhbinghi
Gleamlang
@Lutz64
before I was told it was a gopher, I was describing it as " the language with the beaver on crack"
@jasonwhite5578
As far as the one letter vars, I feel like a lot of devs saw that vars for receivers were excepted as one letter, but then took a mile from that inch. One letter vars for receivers really should be it though. Maybe for loops too, but hey people suck.
@RossPfeiffer
Mascot is a turnoff😂
@ernesto906