Linked by Thom Holwerda on Mon 11th Feb 2013 22:59 UTC
General Development "I feel like writing about the Go programming language (or 'Golang') today, so instead today's topic is computer stuff. For the record, the language I've programmed the most in has been Python, so that’s the perspective I'm analyzing it from." Some good and bad things about Go.
Thread beginning with comment 552220
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: My thoughts on Go
by satsujinka on Tue 12th Feb 2013 17:33 UTC in reply to "My thoughts on Go"
satsujinka
Member since:
2010-03-11

I'm curious why you feel you need an IDE? Go has been perfectly fine in most editors in my experience.

Reply Parent Score: 2

RE[2]: My thoughts on Go
by Nelson on Tue 12th Feb 2013 18:12 in reply to "RE: My thoughts on Go"
Nelson Member since:
2005-11-29

The language doesn't inherently afford you a lot of the expressiveness of other OO languages in their object model. You can't for example, at a glance, tell which interfaces a given "object" (as loose as the term is used in Go) implements.

That's where I think an IDE and the language can split the difference and make up for that. There are other small instances too like the fact that IDEs can help remove the stigma surrounding some of the more exotic syntax choices. That's valuable too.

it is my belief that a programming language is nothing without the tooling, a complete stack from beginning to end.

Reply Parent Score: 3

RE[3]: My thoughts on Go
by satsujinka on Tue 12th Feb 2013 18:15 in reply to "RE[2]: My thoughts on Go"
satsujinka Member since:
2010-03-11

Ah, I suppose we'll have to agree to disagree. While IDEs can be important, I feel a language should stand on its own. Which I feel Go does fine on.

Reply Parent Score: 3

RE[2]: My thoughts on Go
by moondevil on Tue 12th Feb 2013 20:20 in reply to "RE: My thoughts on Go"
moondevil Member since:
2005-07-08

I'm curious why you feel you need an IDE? Go has been perfectly fine in most editors in my experience.



For example, list all the interfaces the following type does support:

type Example struct {
afield int
}

func (e *Example) MyMethod () int {
}

Without the help of a tool that searches all visible interfaces and checks if Example fullfils the required set of methods, it is not possible by reading the code to know which set of interfaces are supported by Example.

Reply Parent Score: 3

RE[3]: My thoughts on Go
by satsujinka on Tue 12th Feb 2013 20:40 in reply to "RE[2]: My thoughts on Go"
satsujinka Member since:
2010-03-11

You don't need to know all the interfaces Example implements. You just have to know what the interface you're using requires and if your object has it.

In other words, you're looking at the code backwards compared to how Go works. Which may be an issue if ideal mental models of Go end up being backwards compared to other languages.

Reply Parent Score: 3