Well, I took the person saying "MS is mum on it" as "they are keeping it secret." If they are keeping it secret, that's interesting. But I'm possibly reading into this something that isn't there.
Obviously not an official MS response!
We are using a single threaded lightweight runtime based around call backs. We are completely non-blocking on all IO (including all sensors), and our CPU spends the majority of its time in a very low power mode. Every microsecond of CPU time is accounted for and justified!
I cannot wait until people look at our battery size in mAh.
Sounds like Javascript to me, or maybe something like Erlang. I wonder if we'll be able to install apps on the device or just build external apps for cell phones. What about hooking it up to your desktop/laptop for notifications and stuff? I'm thinking there could be some cool features there.
No comment on anything else mentioned:)
Congratulations for this btw. I'm not an MS fan, but I hope this works for you guys!
Our software was completely written from the ground up. We started with an empty main.c file. :)
A number of us lead software engineers are on hacker news and we all love the latest programming languages. We got a bunch of really super cool stuff in here, but all in straight C and running in very little memory space. We're dying to start an engineering blog, we believe some of the lessons we learned about applying modern software engineering techniques to an embedded device are very valuable. (Fun fact! Embedded Engineers have been avoiding dynamic allocation well before it was cool!)
We're hoping to get proper continuations in sometime soon. :) Our main problem is saving/restoring the stack without losing too much performance! (Cycles equal battery life, I cannot justify pushing for a move to continuations if the battery life hit is noticeable to the user!)
I hope you get your dev blog approved :)
Megabytes? That'd have been nice! :)
Thanks :)
I don't think this is enough info, even for an educated guess. What they're describing (single threaded/callbacks) could even be C/libevent, no?
Edit: Also,
> Every microsecond of CPU time is accounted for and justified!
...for me, this rules out any kind of VM contained language
I would guess C or C++ too.