First chapter of Kernighan and Donovan's new Go book [pdf]

Post by chimeracoder » Mon, Oct 19, 2015, 6:42 PM UTC

seiji wrote: post #44

chimeracoder wrote: post #30

Earlier quoted context omitted.

Yeah, I know 100x is a huge multiplier, but I've actually tracked myself to the extent possible, and that really is the right order of magnitude for me. There are a number of reasons. I find refactoring is way, way simpler. Refactoring in Python feels painful enough that I always put it off until it gets absolutely necessary. With Go, I find it takes way less time, and also less mental energy. The static typing and s…

The static typing and strict compiler (enforcement of imports and lvalues, etc.) works well for my writing style. It seems you more enjoy just "Not Python" than Go itself. Go is still pretty awful and designed without really consulting what would help users. It's just designed for what the creators want, but now millions of people are trying to use it—not just 8 people inside the Nation of Google. It's getting worse…

Post by yokohummer7 » Mon, Oct 19, 2015, 6:50 PM UTC

realrocker wrote: post #4

From the book: "But it has comparatively few features and is unlikely to add more. For instance, it has no implicit numeric conversions, no constructors or destructors, no operator overloading, no default parameter values, no inheritance, no generics, no exceptions, no macros, no function annotations, and no thread-local storage."

  type T struct {
    a int
    b string
    c float64
  }
  
  t := T{c: 1.5}

Post by andmarios » Mon, Oct 19, 2015, 6:52 PM UTC

Omnipresent wrote: post #9

To those in the Go community: - What is Go well suited for other than network programming? - Why might one decide to write the backend API of their web app in Go, compared to say Grails, Python etc.

Post by [deleted] » Mon, Oct 19, 2015, 6:54 PM UTC

yokohummer7 wrote: post #64

realrocker wrote: post #4

From the book: "But it has comparatively few features and is unlikely to add more. For instance, it has no implicit numeric conversions, no constructors or destructors, no operator overloading, no default parameter values, no inheritance, no generics, no exceptions, no macros, no function annotations, and no thread-local storage."

> no default parameter values Hearing this leaves a bad taste in my mouth, because one of the (mis)features I've found in Go is its implicit default value in struct initialization. In Go, you don't get a compile error when you miss some fields while initializing a struct. e.g. type T struct { a int b string c float64 } t := T{c: 1.5} will happily set `t.a` to 0 and `t.b` to an empty string. While this is useful for m…

Post by seiji » Mon, Oct 19, 2015, 6:56 PM UTC

mseepgood wrote: post #57

seiji wrote: post #41

Earlier quoted context omitted.

Most talented people can write 200 "productive" lines of code per day (not copy/paste java boilerplate). So, 100x would mean you are now writing 20,000 lines of code per day.

"One of my most productive days was throwing away 1000 lines of code." — Ken Thompson, Go designer