davecheney

11 ms·

61.
by davecheney 11y ago
Everyone knows the GIL as Python's big problem; dependency management is Go's big problem -- it's an analogy, that's it, nothing more.
62.
by davecheney 11y ago
It's vendoring without rewriting, http://go-talks.appspot.com/github.com/davecheney/presentati...
63.
by davecheney 11y ago
Bloated.
64.
GopherCon 2015 – First speakers announced(blog.gopheracademy.com)
6 points by davecheney 12y ago|0 comments
65.
by davecheney 12y ago
What a feckless comparison. Don't mistake something taking more time with something being more complex.
66.
by davecheney 12y ago
I can confidently predict the author will decide that Rust has some nice attributes, but pales in comparison to D.
67.
by davecheney 12y ago
If you want a more complex Java you can have Scala. Scala remains hostile to newcomers with an almost vertical learning curve. I don't think anyone can seriously argue that commercial programmers need a more complex language.
68.
The Go Programming Language by Brian W. Kernighan, Alan Donovan(amazon.com)
396 points by davecheney 12y ago|253 comments
69.
by davecheney 12y ago
The use of the opening phrase "We're not willing ... " implies that the OP interpreted my statements as a policy of the wider Go team. I have no knowledge of any such policy and represent only myself on stage. You can think w
70.
by davecheney 12y ago
Go is an open source project, Canonical sponsor Go in part by paying my salary. Canonical have been building products in Go for three years.
71.
by davecheney 12y ago
I am not a member of the Go team, just a contributor. I represent only my own opinions, please don't put words into my mouth.
72.
by davecheney 12y ago
You can read the original commit on Gerrit, it's less explodey. https://go-review.googlesource.com/#/c/5652/
73.
by davecheney 12y ago
No, this was unrelated. SP, PC and FP are virtual registers, from the POV of the assembler. On _some_ architecture those words have real meanings, like RSP on intel, but on others they are just conventions. I don't think Keith's r
74.
Practical public speaking for Nerds(dave.cheney.net)
3 points by davecheney 12y ago|0 comments
75.
How does Go handle select statements when multiple channels are ready?(blog.matttproud.com)
3 points by davecheney 12y ago|0 comments
76.
AWS Elastic Beanstalk Supports Go(aws.amazon.com)
5 points by davecheney 12y ago|0 comments
77.
by davecheney 12y ago
13 softball questions with Mark Cuban. What a load of crap.
78.
by davecheney 12y ago
We have always been at war with East Asia, like my status!
79.
Gopher Gala 2015 Finalists(gophergala.com)
1 points by davecheney 12y ago|0 comments
80.
by davecheney 12y ago
1.75gb is three cd roms. It's not big data. 1.75gb of ram is less than the virtual address space for 32 bit windows Xp, it's not big data. Protip: if it fits on the computer on your desk, it's not big data.
81.
by davecheney 12y ago
The 90's called, they want their prediction back.
82.
by davecheney 12y ago
1.75gb is not big data. It's not even small data.
83.
by davecheney 12y ago
With all the wrong in this world at the moment you want to speculate on additional imaginary evils? You need to get your priorities straight.
84.
Go 1.4.1 has been released(groups.google.com)
3 points by davecheney 12y ago|0 comments
85.
Errors are values(blog.golang.org)
138 points by davecheney 12y ago|135 comments
86.
by davecheney 12y ago
Citation needed please. Ian Lance Taylor, a core member of the Go team has revised and replied to many of the generics debates on go-nuts.
87.
by davecheney 12y ago
What horse pucky. The first Unix systems were used by Bell Labs' patent department to process patent applications. It was this first customer of the Unix group that sponsored the development of Unix for many of its formative years.
88.
by davecheney 12y ago
Wait til Keith discovers Go passes arguments on the stack, totally ignoring SPARC's register windows.
89.
by davecheney 12y ago
When will this madness stop? Will systemd not be satisfied til it has subsumed the universe into one great pid 1 singularity?
90.
by davecheney 12y ago
This is perhaps a bit misleading. What was achieved in 1.3 was a collector that was precise for the heap and the stack. In doing so it enabled the new stack copying mode for more efficient stack growth. However not all code could take advan

More ›