Misleading title<p>> Just to be clear Node.js does not run IN a spacesuit. It does however support spacesuit operations, processing, logistics, etc...<p>(source: <a href="https://twitter.com/CollinEstes/status/741994459349417984" rel="nofollow">https://twitter.com/CollinEstes/status/741994459349417984</a>)
Important addendum: Node is not for real-time safety-critical systems <a href="https://mobile.twitter.com/d4rw1n1s7/status/743010594786250756" rel="nofollow">https://mobile.twitter.com/d4rw1n1s7/status/7430105947862507...</a>
Made me think of Lisp at JPL, one of my favourite software-dev history stories.
<a href="http://www.flownet.com/gat/jpl-lisp.html" rel="nofollow">http://www.flownet.com/gat/jpl-lisp.html</a>
Presentation at EnterpriseJS Austin:<p>Spacesuits and Node.js - How open source will change NASA<p><a href="https://vimeo.com/168064722" rel="nofollow">https://vimeo.com/168064722</a>
Forth code ran on the Rosetta lander's space qualified, radiation hardened, 16-bit Harris RTX2010 processor. The OS could even be changed via the radio link by writing new code to EEPROM [1].<p>Let Node try that ;) On second thought...<p>[1] <a href="http://articles.adsabs.harvard.edu//full/2003ESASP.532E..72B/0000072.002.html" rel="nofollow">http://articles.adsabs.harvard.edu//full/2003ESASP.532E..72B...</a>
It's always nice to feel appreciated, but the validation-seeking pile-on in that Twitter thread is a little awkward.<p>Reward yourself with a cookie then go read your Github Issues tab, guys...