<p>So I spent my night after the little one went to bed last night installing/configuring Go, Git and Atom (with Go-Plus), and tested a quick hello world web request handler to make sure everything is working...which it is!</p>
<p>My first question is...is there a way to have my Atom editor also have shortcuts/ability to do "go build" or "go install" commands either on demand or automatically, and possibly even the ability to execute the compiled .exes?</p>
<p>I'm looking to have as much functionality done from one program (Atom) as possible, and rely less on command windows. </p>
<p>Disclaimer for 10 years I've been immersed in the Microsoft stack and have 0 experience in anything else so that's why I've decided to learn Go and also why I'm so clueless</p>
<hr/>**评论：**<br/><br/>dlsniper: <pre><p>Use any JetBrains IDE (including the free ones) with the Go plugin for them and they should help you get off the ground with much less configuration than other editors. </p></pre>kavehmz: <pre><p>I am also using Atom with "Go Plus", "go-rename" and "Script" packages. Works fine for me.</p>
<p>Especially if you are familiar with Atom and how to customize it, you might like it better than some other environments.</p></pre>Stryfex19: <pre><p>So far my experience with Atom seems great. There are some odd things with auto-complete that I find weird though like if I type "func ma" and the autocomplete comes up to select the "main()" function, I hit enter and end up with "func func main() {}" which I then have to delete the first func...I'm sure I'll get used to how to manipulate it properly.</p>
<p>It seems like a good editor choice so far</p></pre>Ainar-G: <pre><p>This doesn't answer your question, but if you've been immersed in the Microsoft stack for so long, why not proceed with it and use <a href="http://code.visualstudio.com/" rel="nofollow">VS Code</a>? Of all editors I've tried, it seems to have the nicest, most seamless integration with Go tools. It even has visual integration with the Delve debugger. I myself am a vim+vim-go kind of guy, but if I weren't used to vim so much, I'd use VS Code to write Go code.</p></pre>Stryfex19: <pre><p>Thanks to everyone for the replies! I spent another hour or so with it last night and even after just that little bit more time I'm getting more into the groove and generally getting the hang of the process. I'm excited to get past alot of the "language learning" that I'm currently doing and into building </p></pre>jeffrallen: <pre><p>Go does not need an IDE. Work your way through the Go Tutorial online, and then Effective Go (use Notepad and cmd.exe). When you see the fundamentals of Go and it's tools, then you'll be equipped to decide how much or whether you want an IDE at all.</p></pre>Stryfex19: <pre><p>I've been working through some examples from the book "The Go Programming Language" and it's going great so far in terms of no issues (and the language itself seems great so far) but being in the Visual Studio world for the past 10 years it's tough to get used to spending so much time with CMD heh</p></pre>dbud: <pre><p>Go is definitely more geared towards "the unix way" of command lines and hand running stuff.<br/>
All my go dev iterations are basically: go install ./... && appname<br/>
where app name is the executable i want to run.<br/>
Bouncing the app consists of me hitting Ctrl-C, Up arrow, and enter. </p>
<p>Not as straight forward as hitting F5 (or whatever VS uses these days), but also not that bad. </p>
<p>As for editors doing this automatically, i haven't seen one.<br/>
Probably due to not having any concept of a project / solution.</p>
<p>You may have luck with Intellij IDEA and the go plugin. </p>
<p>That all said, <a href="/u/jeffrallen" rel="nofollow">/u/jeffrallen</a> is right. Simple editor and command line is probably your best bet. Not sure I'd go as far as Notepad. I use Sublime Text with GoSublime plugin myself.</p></pre>zeroZshadow: <pre><p>install atom-build.
It allows you to throw the go build command behind a hotkey in atom.
terminal is also a nice package, allowing you to start your build executable from inside atom.</p></pre>Stryfex19: <pre><p>oooo thanks, those seem great! i'll install them tonight after work!!</p></pre>izuriel: <pre><blockquote>
<p>being in the Visual Studio world for the past 10 years it's tough to get used to spending so much time with CMD</p>
</blockquote>
<p>So take learning Go as a chance to correct that. As a person who has hired and interview developers in the past one of my major turn offs is if they can't work inside a command line. I get that Windows and Windows development tools don't let you get away with a lot of command line work (and the command line is terrible in Windows). Personally I recommend installing Git Bash (cygwin itself can be an overload when starting out) to get some unix tooling and behavior (and BASH!) and then use ConEmu setting up your tab defaults to run Bash. I recommend working this way and you'll either still not catch on or you end up loving the command line so much you'll wonder why Windows tries so desperately hard to keep you out of it (I feel in love with it, 90% of my work is through a terminal now -- albeit I quit working on Windows machines and got a Mac)!</p></pre>Stryfex19: <pre><p>That's essentially the main motivation for this whole exercise...I'm trying to broaden my skillset and knowledge-base...when you get silo'd into a certain type of work for a long time it tends to shape your thinking and I'm just really in the mood to spruce up my abilities.</p>
<p>not to mention that over the past few years getting a chromebook for my wife, and various android devices, which have both been tastes of an "alternative to microsoft" i've really gotten a sense that I really like that alternative</p></pre>izuriel: <pre><p>Well, welcome to the community. I think your jaunt into new territory is a worthwhile endeavor and I hope that you find it enjoyable. I agree with you comments on being silo'd. I'm working with some Ruby developers that have a hard time seeing past ruby's way of doing things when approaching problems. Most of the time the differences aren't worth bringing up but it would be great if every engineer had at least two languages they specialized in to vary their approaches. </p></pre>
