f2f

22 ms·

181.
Gzip Performance for Go Webservers(blog.klauspost.com)
1 points by f2f 11y ago|0 comments
182.
by f2f 11y ago
yes, that too :)
183.
by f2f 11y ago
back when the plan9 compilers were introduced to the world [0] POSIX 1003 was less than 3 years old. that they didn't change much in their design since is a testament to a) how good they were and 2) how good their authors were. -- 0: f
184.
by f2f 11y ago
point taken. i would love to see the videos of those talks.
185.
by f2f 11y ago
if you want to invoke the America vs Europe rift you'll probably be interested in an earlier talk from the same conference given by Robert Griesemer on the evolution of Go: https://sourcegraph.com/blog/live/go
186.
by f2f 11y ago
no. edit: depends on the company
187.
by f2f 11y ago
both the original article and the Reddit discussion come up in my results (as 1 and 2). the reddit discussion is only 16 hours old. https://www.google.com/search?q=golang%201%20million&rct=j this HN discussion is too re
188.
by f2f 11y ago
I'm sorry but the official name is Go. You can search for "Golang" or "Go Language" with no issue.
189.
by f2f 11y ago
this article discusses how they handled 69GB of heap and up to 6 seconds of pause times: http://blog.golang.org/qihoo the new garbage collector in 1.5 should improve things.
190.
An exercise in profiling a Go program(thornydev.blogspot.com)
88 points by f2f 11y ago|15 comments
191.
by f2f 11y ago
this paper still reads revolutionary now, but imagine how it felt to read it in 1993 and compare it with your average "system" either at home or at work. windows for workgroups was released the same year, while we were struggling
192.
Node9: Inferno kernel with LuaJIT instead of the Dis virtual machine(github.com)
116 points by f2f 11y ago|21 comments
193.
by f2f 12y ago
> Many of the ideas in go were not well understood and had only been demonstrated in research languages prior to go. Its concurrency model and associated primitives, and the automatic interface system were in roughly the same state then
194.
by f2f 12y ago
example session: (llgo) 1+1 #0 untyped int = 2 (llgo) x := 1 x untyped int = 1 (llgo) x++ (llgo) x #0 int = 2 (llgo) import "fmt" (llgo) fmt.Println("hello world") hello world #0 int = 12 #1 err
195.
Llgoi: the llgo repl (towards the bottom of the page)(llvm.org)
1 points by f2f 12y ago|1 comments
196.
by f2f 12y ago
similarly, mdb on solaris is very powerful.
197.
by f2f 12y ago
a few more lines if you just let os.Stdout be the default: http://play.golang.org/p/FDbpCxCskT
198.
by f2f 12y ago
kernighan also wrote the tutorial on the Limbo programming language: http://doc.cat-v.org/inferno/4th_edition/limbo_language/desc... he's obviously good at it, and the perspective of someone not involved
199.
by f2f 12y ago
I was alluding to Ken being the author of the old, as well as one of the authors of the new compiler. In jest :)
200.
by f2f 12y ago
You can't avoid trusting trust. "Ken was here" :)
201.
by f2f 12y ago
what this fine list sorely misses is a true retelling of the "Plan 9 and the echo" story, as found here, on the Plan 9 mailing lists some millenia ago: The Plan 9 and the Echo: http://9fans.net/archive/2001&#x
202.
by f2f 12y ago
the problem with goamz, when i forked it, was that merging changes into canonical's bazaar cvs was very hard to do. that was before github and pull requests became de-rigeur, so i'm a bit dated. still, very few of canonical's
203.
by f2f 12y ago
<snark> had to be hundreds of thousands because you didn't come out of the gates with a decent design and you had to wing it for the last 6 years </snark> ;)
204.
by f2f 12y ago
TIL that the hardest thing to do in computer science is to learn something new and different.
205.
by f2f 12y ago
don't be discouraged, it's par for the course. we're talking about quality lines of code: debugged, qa'd, and working as expected. perhaps even after the customer has had a chance to peruse the beta. you will be surprise
206.
by f2f 12y ago
oops, sorry, downvote brigade. :)
207.
by f2f 12y ago
what language progress? this is Go we're talking about :) (before the downvotes start raining, my joke is referring to the Go compatibility promise, not the lack of whizbang blinkenlights)
208.
by f2f 12y ago
cool! i really like what you're doing.
209.
by f2f 12y ago
i can't figure out which one of the several Go9P implementations you started with. or is this something you rolled out yourself? any differences between this and others?
210.
by f2f 12y ago
i'm sorry but "i'm no expert" is not an excuse for trying to change people's minds. that's how anti-vaxxers are born.

More ›