ANI Compiler

http://code.google.com/p/anic/
* Faster than C
* Fully parallel threaded code
* Optimized dataflow language
In fact, ANI is designed to abstract away from the idea of an "algorithm" altogether, which further goes to demonstrate that you can't neatly apply explicit ideas of parallelism to an implicitly parallel language.

I'll refute their FAQ point by point:
http://code.google.com/p/anic/wiki/FAQ
Q: How do I pronounce ANI / anic? What does ANI stand for?

A: ANI is pronounced just like the feminine name "Annie"; anic is just "panic" without the 'p'.

ANI stands for "Animus", but apart from the animus being a neat concept, the name was chosen because it generates reasonably clean search hits, in an attempt to avoid the name stomping fiasco that Google instigated with Golang.

Oh, that would be wrong:
About 133,000,000 results for ANI
http://en.wikipedia.org/wiki/ANI plenty of acronyms
And the idea that ANI is derived from animus is also wrong, since the latin root is ANIM->SUFFIX, i.e. ANIM-al, ANIM-ate, ANIM-ate
http://www.wordinfo.info/words/index/info/view_unit/2388/


__________________
Orbis terrarum delenda est

Q: Faster than C? How is that possible?

A: Traditional programs are single-threaded; in most cases, this is the category that C programs fall into.

In that sense, however, these programs are limited in the resources they can leverage; they can't take advantage of parallel execution on multiprocessor architectures, the kind that we're seeing become ever more prevalent today (and this trend looks like it's here to stay). Of course, if you're comfortable with juggling chainsaws, you can write multithreaded programs in C, but ask anyone who's worked on a large multithreaded system written in C and you'll see them cringe. C is an inherently single-threaded language with ugly multithreading support tacked on once the goof of originally omitting it was obvious. That means ugly code and cluttered binaries that will never run as fast as they could in a language designed from the ground up to be based around parallel execution.

That's the kind of language ANI is; in fact, ANI is so parallel that it's actually difficult to write traditional sequential programs in it. But the point is you should never have to: single-threaded programs are a thing of the past. The future lies in concurrency.

Parallel program never achieve linear speedup. Its hardware limited. This page provide no benchmarks to compare to. Do they mean, that poorly written single-threaded C is slower than multithreaded  ANI program? I'll like to see what they base this off. This is pretty bold claim for an alpha language thats "so parallel" that it needs no optimizations to beat GCC.



__________________
Orbis terrarum delenda est