"Given this interesting first result, we plan to test a number of additional languages using the same procedures."
Hopefully they'll use larger sample sizes too. This one involved 18 people across 3 groups.
436 karma · joined October 13, 2010
"Given this interesting first result, we plan to test a number of additional languages using the same procedures."
Hopefully they'll use larger sample sizes too. This one involved 18 people across 3 groups.
I'm surprised that there was only one AI in the competition that did this. We were all expected to use this strategy in my class. Once everybody's figured this out, it becomes a game of:
- Who can think ahead the most turns? - Who has the best "am I winning?" heuristic function? (For Mancala this function is fairly obvious, but for many games it's not.)
(Native Client is also a possibility.)
http://blogs.msdn.com/b/oldnewthing/archive/2005/01/14/35294...
In Go, it's even easier to recognize ignored error codes because you tend to have fewer levels of indentation and sometimes an explicit "_" when you're discarding a return value.
It did and still does make me wonder, though.
If Go adds support for generics, manual memory management could be provided by a third party package.
http://thread.gmane.org/gmane.comp.python.pypy/7303/focus=73...
I would love to see a similar grep-type feature, where I can quickly search through the files in a repository for text. (Yes, I know there's advanced search, but that's so disruptive to my code reading.)
1. Most UTF-8 string operations can operate on a byte at a time. You just have realize that functions like strlen will be telling you byte length instead of character length, and this usually doesn't even matter. (It's still important to know.)
2. UTF-16 is still a variable-width encoding. It was originally intended to be fixed-width, but then the Unicode character set grew too large to be represented in 16 bits.
I'm always interested in alternatives to Make because I just find it so painful. However, I'd say that only about half of Make-related pain comes from its dependency management. The other half, to me, is in using its language, and Ninja doesn't seem to do anything to ease that pain. Its manual says: "You should generate your ninja files using another program." That seems like a bad sign to me.
Tools like CMake can be helpful when there are lots of configurations available and dependencies to check, but on a small project I want to write a quick script that will just work. CMake and its ilk add another layer of complication that I don't want to have to deal with most of the time.
Not only will headers including headers cause files to rebuild unnecessarily, but it can cause build times to increase simply because the compiler has to compile all those extra headers each time they're included in a source file. (Precompiled headers can help, but they aren't always an option.)
I think Go actually gets this right: its syntax doesn't require any wacky characters, but it allows identifiers to consist of any Unicode characters classified as letters or numbers. The syntax caters to the lowest common denominator, but if I really want to name my variables in Greek, I can.
I'm not saying that those benchmarks don't have value, but saying that Go's barely faster than the best dynamic languages doesn't ring true to me.