Arduino is an implementation of the hardware and the toolchain (I think it's AVR based). You can probably stick a PIC/LPC on it and cross-compile the software and have the same result.
Same as you can compile cygwin programs to run on UNIX...
Our IE6 support policy was tell all our paid up clients 6 months before 1st Jan 2010 that we'll be dropping IE6 support. We have a 6 month lead on changes.
The only complaints we have are from people with heavy Citrix on Win2k investments as IE7+ isn't supported on Win2k and some people who are so poorly invested that they don't want to upgrade (bad client indicatorpotentially)
The basic outcome is that we won't do anything crazy that destroy it intentionally, but if it breaks, you will have to pay us extra to fix it.
I trialled this a while ago. Whilst good in principle, you lose a lot of the power of the web forms view engine, particularly with the strong-typing of hyperlinks and routing integration. Not only that, it's written in F# which no-one can maintain effectively as noone (affordable) knows it.
a) BMI is not a good measure of anything. It is based on a flawed methodology [1]. Look at athletes for a concrete example.
b) The data they provide is pretty random and is generalised too much by country to be relevant. If it was all people plotted as points it might have some value, but not just countries. Not enough data to be reliable.
c) I'm fat and I don't eat any fast food. Everything I eat, I cook. Most of it, I grow! I do scary amounts of exercise. Why am I fat?
Firstly, I've never had a malloc fail because I code very defensively.
If memory is likely to be an issue, you should control the usage of your memory to start with.
Also, the virtual address space is usually bigger than physical memory (on non-crap OS's and libs) so the performance of the memory access (when swap is involved) is an issue before you get to the stage of running out of memory. Last thing you want is MMU faults and time in the kernel to worry about.