News for hackers. Stuff that matters.

A comment on James Webb Telescope will run a proprietary JS interpreter by a bankrupt company. Parent comment

Re:James Webb Telescope will run a proprietary JS interprete... by plopz on Wednesday April 24, 2019 @09:54AM (#19738315)
Yeah, in 2003 this version of js worked with vxworks and didn't leak memory like python. I'm sort of surprised they didn't go with tcl though.
[ Parent | on HN ]
Re:James Webb Telescope will run a proprietary JS interprete... by harshreality on Wednesday April 24, 2019 @10:09AM (#19738473)
The reason they didn't choose tcl had nothing to do with the language.

> 2. An attempt was made to port each scripting engine to the VxWorks real-time operating system on a flight-like Power PC by embedding it into a payload flight software application. TCL was dropped from the study when it could not be successfully ported to VxWorks. JavaScript, Python and G-script were successfully ported and a series of tests with prototype flight software applications were run in order to rank them against the success criteria.

https://www.scribd.com/document/407354589/Event-driven-James...

[ Parent | on HN ]
Re:James Webb Telescope will run a proprietary JS interprete... by cartoonfoxes on Wednesday April 24, 2019 @10:50AM (#19738886)
I would have assumed porting TCL would have been the most straightforward of the bunch. What features made it so difficult to work with?
[ Parent | on HN ]
Re:James Webb Telescope will run a proprietary JS interprete... by plopz on Wednesday April 24, 2019 @10:12AM (#19738495)
Ahh, that makes sense then.
[ Parent | on HN ]