f2f

30 ms·

241.
by f2f 12y ago
Quit whining.
242.
by f2f 12y ago
"at least" is there for a reason.
243.
by f2f 12y ago
"microthreads", channels, and the select statement predate go at least by a couple of decades in Alef, Plan9's libthread, Limbo, Newsqueak, etc.
244.
by f2f 12y ago
> lied to Go and told it there was only one CPU but then you loose all the cool features of channels etc.. channels work just fine in a single-cpu context. concurrency is not parallelism.
245.
by f2f 12y ago
the go side of that paper should be accompanied by this link, always: http://blog.golang.org/profiling-go-programs
246.
by f2f 12y ago
no such large go shops exist.
247.
by f2f 12y ago
gofmt already uses elastic tabstops.
248.
by f2f 12y ago
+1 so hard my keyboard almost broke Every language needs this except lisp and python :) Note that the one trick gofmt has over say indent is that it truly understands go syntax. It's not just a pretty printer
249.
by f2f 12y ago
Great news! This will finally bring Amoeba into the mainstream!
250.
by f2f 12y ago
> But perhaps this has changed in recent versions of go? it hasn't. i meant 'if you build go with CGO_ENABLED=0' but was unclear.
251.
by f2f 12y ago
if you build with CGO_ENABLED=0 then you'll have fully static go binaries on osx (but TLS won't work)
252.
by f2f 12y ago
pleased to make your acquaintance.
253.
by f2f 13y ago
too bad, it can't be changed now. that would require editing a number and recompiling!
254.
by f2f 13y ago
this is the fat-tree connection diagram for one of the cabinets of a CM-5. it was posted on a wall at one of the national labs in the US which had the pleasure of working with a CM-5 around the time War Games was in theatres. People still g
255.
by f2f 13y ago
<T>. they know who they are.
256.
by f2f 13y ago
is this trying to solve a particular problem or just pandering to the "... but generics!" crowd of trolls? because it doesn't look like it's solving anything, it feels positively ugly, and there's no way we'll
257.
by f2f 13y ago
I think they should hold a bake sale.
258.
by f2f 13y ago
the server (mqttsrv) needs GOMAXPROCS>1 for any appreciable changes in the results, otherwise we're just measuring contention in the client. i ran on a 2-core intel desktop running linux.
259.
by f2f 13y ago
loadtest for 100 500 750 1000, X*Y below means X = loadtest GOMAXPROCS and Y = mqttsrv GOMAXPROCS: 1x1 80735 67696 67068 66585 2x1 64380 76531 31346 43268 4x1 77613 73794 72759 43263 8x1 77813 64197 32899 46960 1x2 71641 72521
260.
by f2f 13y ago
i see no mention of "concurrency" in that article. i see that the go programs make heavy use of goroutines so why were they run in "single threaded" mode? just testing their mqttsrv with various levels of GOMAXPROCS rewa
261.
by f2f 13y ago
literally prior art: http://research.swtch.com/qart and this one has the benefit of allowing you to make a qr code with your face on it :)
262.
The Business Card Raytracer in Go: An Optimization Story(kidoman.com)
10 points by f2f 13y ago|1 comments
263.
by f2f 13y ago
that's a problem for those using 0 to terminate a string. if you don't there's no issue. you can read DMR's historical perspective on choosing 0 as a string terminator here: http://cm.bell-labs.com/who&#x
264.
by f2f 13y ago
excerpt from the author on go-nuts: "Writing in Go continues to be the best part of an all-around very interesting project."
265.
by f2f 13y ago
go's goroutines are coroutines :)
266.
by f2f 13y ago
i was referring to recent examples such as python 3.0, perl 6, or even, say, apache 2.0. eventually they were usable, but the blood sweat and tears involved did not make for cute blog posts such as the one we're commenting on.
267.
by f2f 13y ago
eventually, within the context of the `go vet` tool, the http://godoc.org/code.google.com/p/go.tools/go/types package may be used to analyze interface conversions ("I said I expected interface type
268.
by f2f 13y ago
it wasn't accidental -- it was written on purpose by a programmer (a conversion from Writer to WriteCloser). it was immediately acknowledged as an error and eventually may be caught by the standard code examining tool "vet".
269.
by f2f 13y ago
ironically, that's not the common experience; the term 'second system syndrome' was coined for a reason. "allowed to drop functionality", as used by you, is a strawman -- the team _added_ functionality to the part t
270.
by f2f 13y ago
If you're familiar with Go you can read the source of the apply function here: the loadKernel function reads in the kernel and builds a symbol table looking for the bsd_ast and current_thread symbols here: https://code.googl

More ›