Mods, please add (podcast) warning to title. There is no transcript.
Creating the Go Programming Language [audio]
121–130 of 135 posts
Re: Creating the Go Programming Language [audio]
#122Earlier quoted context omitted.
I feel people gave Golang attention because it was a good language. It also has the best standard library I’ve ever seen.
Like a standard library that doesn't even have a max function for integers, or a set type?
Now look at the standard library and appreciate the fact that it comes with every crypto algorithm that are useful, heck it even comes with a crypto random function and a TLS implementation! Wait, it actually comes with a http(s) library. And with a json serializer/deserializer as well. Who does that?
Re: Creating the Go Programming Language [audio]
#123Earlier quoted context omitted.
Like a standard library that doesn't even have a max function for integers, or a set type?
how easy to fuck up a max function? Now look at the standard library and appreciate the fact that it comes with every crypto algorithm that are useful, heck it even comes with a crypto random function and a TLS implementation! Wait, it actually comes with a http(s) library. And with a json serializer/deserializer as well. Who does that?
> Who does that?
Have you taken a look at the Python standard library?
Re: Creating the Go Programming Language [audio]
#124I write primarily in Go, I have to admit that I can't stand the name of it. When doing a search I constantly have to write "go golang" in my searches to get relevant results. It's too generically named, like naming something "The"
Re: Creating the Go Programming Language [audio]
#125Earlier quoted context omitted.
Because, the complexity doesn't go away, gets dumped into developers that keep re-writing boilerplate libraries that kind of compensate for the lacking features. It happens all the time. Language gets introduced at the sound of simplicity trumpet, tons of boilerplate libraries eventually appear, then if the language manages to make it in the mainstream, half baked features get introduced 'cause backwards compatibilit…
Well, boilerplate is a nuisance, but it is cheap. It’s not generally where your bugs are coming from (and certainly not your most insidious bugs)—they come from your complexity, especially your incidental complexity. In exchange, Go is a very easy language to learn, which is an important property for software development teams—you don’t need to restrict your hiring pool to candidates with experience in $language; you…
Java was once like Go, and ironically DisVM also had support for Java, back in those days.
Re: Creating the Go Programming Language [audio]
#126Earlier quoted context omitted.
I see very little marketing for Go. Compare, for example, to C# when in came out, or Java when it did.
The marketing advantage is largely from being associated with Google and Pike and Thompson. That's a good way to get the world to spread the word for free.
Re: Creating the Go Programming Language [audio]
#127Earlier quoted context omitted.
They talk about it at Google IO, for example.
Go only has the use that it does because of Google marketing, which the only examples given are talks at Google IO? Google has the most efficient marketing team in the world, to have done that much with that little effort...
Re: Creating the Go Programming Language [audio]
#128Earlier quoted context omitted.
how easy to fuck up a max function? Now look at the standard library and appreciate the fact that it comes with every crypto algorithm that are useful, heck it even comes with a crypto random function and a TLS implementation! Wait, it actually comes with a http(s) library. And with a json serializer/deserializer as well. Who does that?
Again that's the ethos of Go. In the many years I spent writing C++ or Python or Haskell I never had to write a max function because it's already there. I don't even need to think about it. And I can compose it easily to form more sophisticated things. > Who does that? Have you taken a look at the Python standard library?
Re: Creating the Go Programming Language [audio]
#129Earlier quoted context omitted.
Well, boilerplate is a nuisance, but it is cheap. It’s not generally where your bugs are coming from (and certainly not your most insidious bugs)—they come from your complexity, especially your incidental complexity. In exchange, Go is a very easy language to learn, which is an important property for software development teams—you don’t need to restrict your hiring pool to candidates with experience in $language; you…
The usual Go answer, Java boilerplate bad, Go's boilerplate good. Java was once like Go, and ironically DisVM also had support for Java, back in those days.
Re: Creating the Go Programming Language [audio]
#130Earlier quoted context omitted.
Avoid messy, gobbledygook, weak and no typed programming languages along with giant bloatware languages.
When Go fanboys say stuff like "avoid weak and no typed programming languages" in relation to Go, it just shows they don't know much about type systems. "No typed programming languages" aren't a thing. Some type is inherent to any programming language that runs on a computer, because at some point you have to shove the data into a range of memory and it will either fit or it won't. Assembly has types. They are very w…