> compared to C it is safer. I never saw a segmentation fault
Well, yeah, it has a GC so it kind of gets that "automatically", I was thinking more about the type system side of things.
And compared to C almost anything is indeed safer.
> I prefer go to python or javascipt. It's far too easy to make errors in them.
That's fair, but these are both dynamic languages, so almost anything with any level of static typing beats them in this regard, I was interested if Go does anything beyond that.
Not to say these are not fair points, but nothing a whole host of other languages haven't provided before Go.
Not only static typing. I just found a bug in an open source python tool that crashed because of a missing member variable in a class. You have to assign a value in the attribute to create it. It requires careful programming to not get such errors. It is also easy to accidentaly create a member variable.
The time you gain by being able to hack some code together is lost by these types of error unless you are a very disciplined programmer.
Another kind of error with python is with blocks defined by vertical alignment. It is easy to make errors when you copy past code and the alignment is not corrected.
When you are under pressure or tired, your discipline may weaken. And this is difficult for inexperienced programmers.
You don't have these problems with go and the normalized formating helps a lot.
Well, yeah, it has a GC so it kind of gets that "automatically", I was thinking more about the type system side of things. And compared to C almost anything is indeed safer.
> I prefer go to python or javascipt. It's far too easy to make errors in them.
That's fair, but these are both dynamic languages, so almost anything with any level of static typing beats them in this regard, I was interested if Go does anything beyond that.
Not to say these are not fair points, but nothing a whole host of other languages haven't provided before Go.