Bigloo/CHICKEN differences

This page has the goal of listing the principal differences between CHICKEN and Bigloo, an alternate implementation for the Scheme programming language.

You can find more information about Bigloo at:

Supported language
Static type annotations
Bigloo has a notion of static type annotations, which can be added to the source code. If type annotations are provided by the user, Bigloo can statically type check the program and reject programs that do not type check.
Availability of continuations
Bigloo doesn't have first class continuations by default, because call/cc is difficult to compile efficiently. There's an optional compiler flag for it, and the Bigloo authors recommend the use of the bind-exit form.
SWIG support
CHICKEN has SWIG support, Bigloo does not. This may make it easier to create wrappers around C libraries for CHICKEN than it is for Bigloo.

Compiling
Code optimizations
Bigloo is designed as an optimizing compiler for strict functional languages, and is much better at static optimizations than CHICKEN. For example, the core language compiler of Bigloo has been used to efficiently compile ML programs.
Backends for code generation
Bigloo has C, Java, and C# backends. CHICKEN talks to C, and can talk to C++ to some degree. Objective-C support via the objc egg.

Installation
Platforms for which binaries are provided
Bigloo provides binaries for Fedora, Debian, Ubuntu and MS Visual Studio platforms. CHICKEN is included in Debian and Ubuntu but for other platforms you have to build from source.
Platforms supported
TODO: Integrate this with the previous item. Bigloo may not provide the binary you want for your platform. For instance, Cygwin and MinGW / MSYS. In that case you'll have to build Bigloo from source. Back in the day, that required a small amount of black magic due to compiler flag quoting or some such. I think the answer was to double the number of slashes specified or something. I don't know if it's a problem anymore, if anyone fixed that wart. There's stuff in their mailing list archives about it in any event.
Build system
Bigloo's build is based on GNU Autoconf. The Visual Studio build of Bigloo is not in their source pool, and judging by the past 2 years of observation, never will be. It is maintained by Yannis Bres, who does good work, but that work lags the main Bigloo releases. CHICKEN runs on many platforms with 1 build, including Visual Studio, MinGW / MSYS, Cygwin, Linux, and Mac OSX. The build is in the source pool, is publically available / fixable, and is always up to date with current CHICKEN releases on all platforms.

Miscellaneous
License
Bigloo's license is GPL. CHICKEN's is BSD.
Main developers
Manuel Serrano, the principal Bigloo author, and Felix Winkelmann, the principal CHICKEN author, are both easygoing, easy to work with, and responsive to community bug reports + improvement requests or offers.
Community size
Bigloo's community is noticeably smaller than CHICKEN's, with fewer resources going into things like organizing wikis, developing extensions, maintaining cross-platform builds, etc. CHICKEN's eggs are a clear advantage here.