Working on it.
The United States is paradoxically home to some of the world’s biggest tech companies and yet doesn’t have enough people studying computer science to fill those jobs.
The U.S. will have 1 million open computing jobs by 2024, according to a recent report by the App Association.
In 2013, the Obama Administration issued a similar statistic estimating that there would be 1.4 million computer science jobs even sooner — by 2020 — but fewer than 400,000 people will graduate with the right skills to fill them. Read more (7/21/17)
follow @the-future-now
Top 10 Cool Gadgets You Can Buy Now On Amazon
Our newest communications satellite, named the Tracking and Data Relay Satellite-M or TDRS-M, launches Aug. 18 aboard an Atlas V rocket from our Kennedy Space Center in Florida. It will be the 13th TDRS satellite and will replenish the fleet of satellites supporting the Space Network, which provides nearly continuous global communications services to more than 40 of our missions.
Communicating from space wasn’t always so easy. During our third attempt to land on the moon in 1970, the Apollo 13 crew had to abort their mission when the spacecraft’s oxygen tank suddenly exploded and destroyed much of the essential equipment onboard. Made famous in the movie ‘Apollo 13’ by Ron Howard and starring Tom Hanks, our NASA engineers on the ground talked to the crew and fixed the issue. Back in 1970 our ground crew could only communicate with their ground teams for 15 percent of their orbit – adding yet another challenge to the crew. Thankfully, our Apollo 13 astronauts survived and safely returned to Earth.
Now, our astronauts don’t have to worry about being disconnected from their teams! With the creation of the TDRS program in 1973, space communications coverage increased rapidly from 15 percent coverage to 85 percent coverage. And as we’ve continued to add TDRS spacecraft, coverage zoomed to over 98 percent!
TDRS is a fleet of satellites that beam data from low-Earth-orbiting space missions to scientists on the ground. These data range from cool galaxy images from the Hubble Space Telescope to high-def videos from astronauts on the International Space Station! TDRS is operated by our Space Network, and it is thanks to these hardworking engineers and scientists that we can continuously advance our knowledge about the universe!
What’s up next in space comm? Only the coolest stuff ever! LASER BEAMS. Our scientists are creating ways to communicate space data from missions through lasers, which have the ability to transfer more data per minute than typical radio-frequency systems. Both radio-frequency and laser comm systems send data at the speed of light, but with laser comm’s ability to send more data at a time through infrared waves, we can receive more information and further our knowledge of space.
How are we initiating laser comm? Our Laser Communications Relay Demonstration is launching in 2019! We’re only two short years away from beaming space data through lasers! This laser communications demo is the next step to strengthen this technology, which uses less power and takes up less space on a spacecraft, leaving more power and room for science instruments.
Watch the TDRS launch live online at 8:03 a.m. EDT on Aug. 18: https://www.nasa.gov/nasalive
Join the conversation on Twitter: @NASA_TDRS and @NASALasercomm!
Make sure to follow us on Tumblr for your regular dose of space: http://nasa.tumblr.com
Many of the functions for general operations are distributed across a bunch of objects and keywords in JavaScript. This increases the cognitive load and increases the number of times a language operation needs to be looked up. Here are a few quick examples:
const obj = { property1: 'value1', property2: 'value2', }; delete obj.property1; Object.preventExtensions(obj); try { obj.property3 = 'value3' } catch(e) { console.log(e.message); } console.log(obj); // { property2: 'value2' }
Reflect simplifies this by providing a consistent API for all of the operations:
const obj2 = { property1: 'value1', property2: 'value2', }; Reflect.deleteProperty(obj2, 'property1'); Reflect.preventExtensions(obj2); const succeeded = Reflect.set(obj2, 'property3', 'value3'); if (succeeded !== true) { console.log('Failed to set "property3", obj is not extensible'); } console.log(obj2); // { property2: 'value2' }
Notice how Reflect.set does not return an error and returns if the value was set instead. Even for basic operations, reflect can help clarify the code more
Those were just a few examples, you can view the full list here. Since Reflect provides a consistent API for many operations, it should generally be used instead of all the separate interfaces when it is available. There are exceptions when the syntax is more clear though; except for cases like the above, setting variables with obj.a = 'value' is usually clearer than Reflect.set(obj, 'a', 'value'). It is supported in all browsers including MS Edge, but not IE 11.
Github Location: https://github.com/Jacob-Friesen/obscurejs/blob/master/2017/reflect.js
i’m scrEAMING
The Vesta Explorer in Strange New World (USA, 1975 dir: Robert Butler).
someone take Gorn away from him before he loses his mind
Meme of the day.
Thank you to @djmakproto for the source link, which I could not previously find!
Check it out: https://pennweallotu1975.tumblr.com/post/164528177008/fiber-optic-hoodie-lazyop
Exclusive Rae Sremmurd from Lollapalooza…
via Drew Levin