<p>Not for me.</p>
<hr/>**评论：**<br/><br/>drewmoney: <pre><p>I'm going through the process of learning it as my first language now. I've been in I.T for 10 years though (support and then operations) so I have pretty good I.T knowledge.</p>
<p>I find most information on the web is structured like; "In Java/C/C# you'd do this, but it's different in Golang!" which is pretty useless to me. Not too much is aimed at the true beginner.</p>
<p>Recently finished the Udemy course by Todd McLeod that I really liked as he just talked about the language and didn't go into every other language. He also starts at the very start and assumes very little.</p>
<p>I'm only ~6 weeks in to learning this and I have a long way to go, but for now I think I made the right choice for a first language.</p></pre>nyoungman: <pre><p>Here's a link to the Go course my Todd McLeod: <a href="https://www.udemy.com/learn-how-to-code/" rel="nofollow">https://www.udemy.com/learn-how-to-code/</a></p></pre>scythelx: <pre><p>Great guy and teacher.</p></pre>neoasterisk: <pre><p>Go is a language that you can only truly appreciate once you've experienced the frustration with the existing languages and ecosystems. That said, it's simplicity makes it a pretty good first language. (What is a method? Just a function that you "attach" on a struct.) </p>
<p>Also it's engineering design approach, tooling and ecosystem will likely train better the students into good practices (testing, profiling/benchmarking, writing examples and good docs, sharing code and working with others) that some programmers take for granted.</p>
<p>In addition students that learn another language after Go will probably have an easier time understanding ideas like Object oriented design and functional programming since they've been already exposed to a basic form of those in Go.</p>
<p>Furthermore, Go is also going to be the ideal language to use for classes such as Distributed systems where Go's concurrent primitives can shine while it's simplicity will help students focus on what's important for the class (and not have to deal with say freeing memory).</p>
<p>At some point, It is quite likely the students that learnt Go as their first language will get enchanted by the buzzwords and features of other languages. This is exactly the journey they have to go through in order to grow and learn new ways of thinking. It's very important and Go, like a good teacher, will have enabled them to do that. Then some of them, after a few years, they might realize that they don't need all that jazz in order to be effective. They might ask themselves if Go was "right" all along.</p></pre>CaptaincCodeman: <pre><p>I agree, it's not fair that you get to learn Go <em>first</em>. You should have to suffer the other languages and ecosystems and frustrations first so you will truly appreciate the elegance and performance :)</p>
<p>I've used everything at some point to verying degrees: Assembler, COBOL, Pascal, SmallTalk, BASIC, C#, Java, Python, JavaScript, Go.</p>
<p>Go is by far my favourite.</p></pre>comrade_donkey: <pre><p>If you're going to be teaching programming, there's two ways you can begin: teach a language in the context of informatics (how computers operate, memory representations, algorithms, etc) or teach a language for productivity, i.e. "how do I X".</p>
<p>My opinion is that Go is a very good fit for the first case. Python/Ruby/JS/etc are more suited for the second.</p></pre>forgiv: <pre><p>Absolutely. </p></pre>drvd: <pre><p>Yes.</p></pre>qu33ksilver: <pre><p>Oh .. not again..</p></pre>fullwedgewhale: <pre><p>I think that's a very valid question. My personal opinion is "I'm not sure." On the one hand it's a fairly comfortable language to work with that seems to work in a way that makes sense to me. On the other hand it has a lot of features that are difficult to appreciate until you've worked in other languages. My first languages were assembler, pascal and C++. I'm only mildly scarred for life.</p></pre>Partageons: <pre><p>Your comment doesn't seem to appear in the thread. Just testing whether I can reply to it.</p></pre>fullwedgewhale: <pre><p>Yes you can.</p></pre>Partageons: <pre><p>That is weird. I can see your comments in my inbox and on your profile page, but if I click "permalink" or "context" it takes me to a page with the whole thread (except your comments) in the "you are viewing a single comment's thread" style.</p>
<p>Anyway, good point. Still, if it has lots of features that make you appreciate it compared to other languages, does that not make it superior to those languages (and therefore good as a first language)?</p></pre>fullwedgewhale: <pre><p>I think that's a good point. I don't think of languages as being superior or (conversely) inferior, just better suited to certain problem domains. I'm coming to Go as a very well seasoned programmer who has worked in several languages, and when I use it I feel I'm having an adult conversation with the computer. One feature I think a "first" programming language should have is that it can fit in your head. (Outside of libraries you can pretty much recall pretty much all the useful language rules without referring to a book). I think this is also true of Go. It's definitely a better choice than Java or C++, I think. </p></pre>dhdfdh: <pre><blockquote>
<p>Not for me.</p>
</blockquote>
<p>Then why'd you ask?</p></pre>Partageons: <pre><p>Because I might end up teaching people how to code in the future.</p></pre>dhdfdh: <pre><p>Then I guess you won't so why'd you ask?</p></pre>lansellot: <pre><p>I think he knows Go and wants to know if it's a good language for beginners.</p></pre>dhdfdh: <pre><p>But he already said he doesn't think that.</p></pre>lansellot: <pre><p>There are two ways to interpret "Not for me."</p>
<p>Do you think it's a good idea? It's not [a good idea] for me, I don't think beginners should start with Go.</p>
<p>Do you think it's a good idea? It's not for me, I'm not the beginner who wants to learn Go.</p>
<p>This is where the confusion comes from. I think I went with the second interpretation and you the first.</p></pre>Partageons: <pre><p>I meant the second.</p></pre>Codemonky: <pre><p>I'd stay away from duck typing and interfaces until you get the hang of things :)</p></pre>
