What brought me to it was the concurrency. I spent my entire career frustrated by not only how concurrency wasn't more of a thing in popular languages, but also how so many people didn't seem to think it was a problem. I pounced on Go when I heard about it. (Although I am currently fluttering my eyelashes at Halide...)
What made me stay is the clarity and simplicity. So many languages seem to be an exercise in showing off how clever you are, by using x clever pattern. Go doesn't seem to suffer this. If I could just use it for the embedded stuff i do... Chris On Tuesday, 26 February 2019 12:07:58 UTC, Louki Sumirniy wrote: > > I just wanted to jot down and share my personal most important reason, and > make this thread a short sample of the most important aspect of Go that > drove you to learn and use it. > > For me, it was this: I have been tinkering with programming on and off > over the years since I was 8 years old, when a TRS-80 CoCo arrived in my > house, and in all the time, and with many languages, from BASIC, Assembler, > Amiga E (this was the first that really came close to this reason for me to > learn go), C, Python and Vala, but in all of these instances, until Go, I > was unable to do the most important thing, as I have very good visual > thinking skills, but poor attention - to be able to complete even a > relatively simple application. > > My usual problem always was that I would get bogged down in some detail, > forget the bigger picture, and hit some big blocker in this detail and then > basically turn off the computer and go ride my skateboard. I have now > written several useful libraries, and massively extended and rewritten (now > around 80% done) a bitcoin-based cryptocurrency wallet/node server suite. > > Without Go's immediacy and simple, logical syntax and build system, I am > lost. Go may be unforgiving in its syntax and semantics, but this is good > because it's less decisions to make, and its really very possible with Go > to start writing code immediately, and figuring out how to slice up the > pieces and add new parts is far easier than in many other languages, start > from a very simple, vague base and sketch out the details bit by bit. No > other language has had this property that I have encountered before. I > often remark that the language's name and the short-attention-span and high > intelligence of many of its adopters have in common to some degree. > > I think part of it has to do with how one must be explicit with many > things, but at the same time, other places you can skip explications > because of the implicit, also lets you focus on what's important and not so > much distract you with superficial details. > > Many other languages force you to really separate coding and architecting, > Go lets you do it all on-the-fly. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
