4 ms·
> And it can't be very fast at processing images. Why not?
by ChristianBundy 7y ago
> And it can't be very fast at processing images.
Why not?
- _bxg1 7y agoBecause it's a very a CPU-intensive task? It's all relative, but in 2003 JS was one of the worst languages you could possibly use for that. Of course it's moot if they aren't actually planning to use it for that side of things.
- semicolon_storm 7y agoSpeed can vary from interpreter to interpreter. I haven't seen any benchmarks of this interpreter, so we don't know how fast it may be. Maybe their JS interpreter applies some restrictions to the language that greatly speeds it up?
- mathgladiator 7y agoOr has special primitives for CPU intensive tasks.
- vardump 7y agoI very much doubt they JIT anything, because of the associated fault risk. So it's going to be an interpreter implementation. That means inner loops will run rather slowly. It could still use image processing library, sure. I doubt NASA wants to do much image processing on-board in the first place. Mostly just lossless compression and maybe some thumbnailing, if they can't download everything.