|
|
|
|
|
by kick
2003 days ago
|
|
He wrote solutions for Shootout (predecessor to that Debian page) problems a few years ago; a lack of k in benchmarks is not due to a lack of k being volunteered: http://www.kparc.com/z/comp.k k is really fast. Half of the things on the Shakti mailing list are just Arthur getting really excited about how significantly he's beating x or y or z in performance and giving numbers for it. `grep`ping it now I see 40 in half a year that explicitly contain the word "benchmark," though not all of these are comparing to other things (some are just comparing to different k releases), and there are more comparisons without that word. Arthur doesn't work at Kx anymore, by the way. He's at Shakti now. Shakti has a different (but still draconian/non-(A)GPL) license. It probably doesn't have the benchmark clause, but I don't care enough to check (I prefer J to k and don't have a proprietary k on my system). |
|
That's 6 of the programs, there were at-least 4 others ;-)
I lacked and still lack the knowledge to figure out if those snippets are doing what they should.
For example, do those scripts set arg n from the command line and read from stdin? Do those scripts write correctly formatted output to stdout?
What a pity that page does not show measurements for those scripts, and a comparison with some of the C programs written for the benchmarks game.