To say that about me there is nothing interesting would be to overstate the case.

  • FAQ - anic - Faster than C, Safer than Java, Simpler than *sh - Google Project Hosting

    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.

    This is a very interesting idea, which looks to implement the piping algorithms used by network based programs (Houdini, Fusion, etc.) into a programming language.