Since the last blog post, Apilog the language has undergone several more iterations of development, and is now quite different from how it was described in the last blog post (which has now been edited to avoid confusion). If you want to read a short motivation behind the language as it is now, please head to the Why Apilog page in the documentation.

This is an old blog post that has been later edited, so that it no longer describes an older version of Apilog. We have kept the post as it explains some of the motivation behind the project.

Experienced software developers know how much effort it takes to produce highly correct and bug free software, even for relatively simple offline applications. That effort is multiplied for online software services which often have complex, distributed internal architecture and continuously evolving functionality.