A one-second video taken by the Rosetta probe on the surface of a comet

Post by aalleavitch » Wed, Apr 25, 2018, 12:01 PM UTC

iliketosleep wrote: post #30

dehef wrote: post #25

Earlier quoted context omitted.

Observable.of(rosetta) .map(rocket => gravityAssist(rocket,'Earth')) .map(rocket => gravityAssist(rocket,'Mars')) .map(rocket => gravityAssist(rocket,'Earth')) .map(rocket => gravityAssist(rocket,'Earth')) .do(rocket => land(rocket)) .do(rocket => tweetVideo()) .catch(error => kaput(error))

Or just simply: npm install rosetta-67P-rendezvous

Post by Tepix » Wed, Apr 25, 2018, 12:14 PM UTC

tenaciousDaniel wrote: post #31

mark_edward wrote: post #16

Earlier quoted context omitted.

To be fair, people have been studying and predicting celestial movements for millennia, and boiled it down to unbelievably precise mechanical formulae. JS is poorly understood in comparison. I say this to hope you feel better at work. I've been pressed into frontend web work and it's fractal complexity.

JS is poorly understood in comparison This might be the most hilariously ridiculous true statement I've ever heard.

Post by nerdponx » Wed, Apr 25, 2018, 12:23 PM UTC

Post by mkirklions » Wed, Apr 25, 2018, 12:41 PM UTC

bwang29 wrote: post #12

To put things in perspective, the comet, 67P/Churyumov-Gerasimenko, is about 4km in diameter, moving at 135,000kms per hour. Rosetta's rendezvousing with the comet required travelling a cumulative distance of over 6.4 billion kms. Gravity assists were needed from four planetary flybys – one of Mars (2007) and three of Earth (2005, 2007 and 2009) – a long circuitous trip that took ten years to complete. Now back to my…

Post by bjoli » Wed, Apr 25, 2018, 12:47 PM UTC

Tepix wrote: post #34

tenaciousDaniel wrote: post #31

Earlier quoted context omitted.

JS is poorly understood in comparison This might be the most hilariously ridiculous true statement I've ever heard.

In javascript: x == x _ is true. Good. x == !x _ is also true. Oops? And guess what: Array(3)==",," _ is also true. But NaN == NaN _ is false. Math.max()>Math.min() _ is also false! but then again Math.max() Madness, I tell you!