So far i don't like the fact it can't handle interrupts (unless by C code), and that it seem to ignore the C++ FFI completely.
That, and the fact that a garbage-collected language is to be run on a microcontroller - a device that is mostly used for realtime tasks. It won't be good for a quadcopter to go into a garbage collect subroutine during the control loop calculations.
Not a problem if you are aware of the issue, but how many people are?
This would be awful for general-purpose programming, but on a device with only 2.5kb of RAM to begin with you can usually pre-allocate anything that needs to survive that reset. I use this in my keyboard firmware's outer loop: http://atreus.technomancy.us/firmware2
Arduino is c++, and c++ FFI's are really hard. So how does this FFI work ?
You are right, no mention of C++. It's not clear how much of a problem that would be. IIRC wrapping C++ in "extern C" more or less enables C++ functions to be called from C. Don't know about compatibility of Arduino libraries, but possibly this is how Microscheme FFI works.
