Comments for Alson Kemp

Comment on Go experiment: de-noising by alson

alson — Sat, 18 May 2013 16:45:17 +0000

:you actually add even more noise by replacing the for with a while

Generally, agreed. Wanted to try something to see how the code would look/be different.

:I don’t really see the point about this.

I’m not sure if you’re referring to the for/while thing or to the overall experiment. If for/while, the “for” does seem simpler. If you’re referring to the overall post, then, as noted, it was a Gedankenexperiment to see if significant whitespace would be a helpful adjustment (transpilation) to Go.

Comment on Go experiment: de-noising by FUZxl

FUZxl — Thu, 16 May 2013 22:45:29 +0000

IMHO you actually add even more noise by replacing the for with a while in certain situations. I don’t really see the point about this.

Comment on [Synthetic] Performance of the Go frontend for GCC by alson

alson — Sun, 05 May 2013 23:24:46 +0000

I’ll have another go [har har] at that. I did flail at “go build-compiler=gccgo” for a bit before giving up, but I had quite a bit of a time with go/gccgo finding libraries and such, so I gave up and ran gccgo by hand.

I agree on the point about static linking, size and such, but folks who poke at gccgo are going to have similar problems to the ones I experienced. The default behavior is the one I used and, while you could argue that I shouldn’t have used the default behavior, most people will use the defaults…

Comment on [Synthetic] Performance of the Go frontend for GCC by FUZxxl

FUZxxl — Sun, 05 May 2013 23:18:38 +0000

BTW, if you set the appropriate environment variables, you can use go build -compiler=gccgo to compile your executables. Also it seems that you link the go libraries statically. Since gogcc also pulls in the glibc, no wonder the executable is so huge. Maybe try dynamic linking. For benchmarking, try https://github.com/davecheney/autobench

Comment on [Synthetic] Performance of the Go frontend for GCC by alson

alson — Sun, 05 May 2013 22:55:00 +0000

Doh. No, I did not. Just did. Much better. I’ll update.

Comment on [Synthetic] Performance of the Go frontend for GCC by hr

hr — Sun, 05 May 2013 22:12:15 +0000

Did you try “strip mandel.gccgo” ?

Comment on [Synthetic] Performance of the Go frontend for GCC by leecbaker

leecbaker — Sun, 05 May 2013 20:08:24 +0000

I believe GCC tends to inline code much more aggressively than other compilers- this may explain the larger executable.

Comment on HighCharts, Bluff, gRaphael – Javascript charting libraries by Paul

Paul — Tue, 14 Aug 2012 15:52:34 +0000

You may also take a look at simple JavaScript charts – dhtmlxChart. It’s a framework-agnostic library based on Canvas. GPL-licensed (for proprietary projects a commercial license is required, $99 for all of your sites). Demos: http://www.dhtmlx.com/docs/products/dhtmlxChart/index.shtml

Comment on My Apache process is only using one core! by gwern

gwern — Thu, 05 Jan 2012 17:09:14 +0000

Also good for power consumption – if you can put all the processing on one core, the other cores can shut down or at least lower their frequencies.

Comment on ExtJS 4 Models + node.js by olecom

olecom — Mon, 07 Nov 2011 14:44:39 +0000

It seems there is already a project worth looking at: https://github.com/xcambar/n-ext