|
|
|
|
|
|
by angusgr
5533 days ago
|
|
|
At present, even from the home page, source code is only 2 or 3 clicks. Yes, but it's always at the "bottom" of the interface when you drill down. For instance, all of the content is there to make an interface which allows side-by-side comparisons of the implementation of the same problem in different languages. At the moment, you can do that but it involves opening two tabs and clicking forward and back through each language. Who would write those annotations? The annotations were just a throwaway idea. I noticed some of the programs are very well commented, some aren't. Probably good commenting & structure covers a lot of it. Who would do the work to create a series of blog posts discussing the development of each and every program? I'm confused by the rhetorical questions. You seem to be suggesting noone would ever do the work to explain the creation of a program, then you link to a blog post which does just that. |
|
|
Or opening two browser windows and looking side by side - by design the page layouts are narrow to enable side by side comparisons (often I've reformated programs to 80 char width), it wasn't that I foresaw the emergence of small screen iPhone browsing ;-)
> suggesting noone would ever do the work to explain
When something seems peculiar I've pursued contributors for some text to explain what's going on with their program - so my thoughts about this are based on my experiences
http://shootout.alioth.debian.org/u32/program.php?test=threa...
> a blog post which does just that
As an example of something that's been done well, and done independently of the benchmarks game.
Anyone can make that kind of analysis and publish on their blog.
The benchmarks game is a starting point and a source of questions, rather than a definitive answer to every question.