This transformer: https://github.com/ds300/react-native-typescript-transformer
worked perfectly for me so far. You don't have to change your code at all but just add a single file to your project and the packager will do all the rest for you.
I'm surprised that no one mentioned it here already but the whole article smells of submarine marketing[0]. A short back story about calorie reduction then some science and then they casually mention Susan Roberts which uses a tool called iDiet. When you visit the website you will see that Dr. Susan Roberts is the one who created this iDiet tool so... yeah
Do you happen to know how arial refueling works then ? E.g. in this image [1] the jet is flying where I would expect a lot of deflected air to be moving to ? Or is it just deflected much more steeply ?
The other two replies covered your questions well, so I'll just add that wakes don't descend particularly fast. According to the FAA's Pilot's Handbook of Aeronautical Knowledge[1] (page 14-28), "Tests have also shown that the vortices sink at a rate of several hundred feet per minute, slowing their descent and diminishing in strength with time and distance behind the generating aircraft."
Considering the Challenger's encounter with the A380's wake, it took 1-2 minutes for the Challenger to hit the wake, so the wake probably had 1-3 minutes to make the 1000-foot descent. That very roughly fits the expected "several hundred feet per minute" descent rate.
Considering the case of refueling, the wake's motion downward is much slower than the aircrafts' horizontal motion, so it wouldn't have descended much by the time it's left behind entirely.
being close is relatively safe from wortexes - there still is some other turbulence to consider, but the standard turbulent flow caused by drag is chaotic so it'll shake you but will 'even out'
Is there a chance that some day your work (expo) will be merged with react native ? Conceptually, I think you are doing what people would expect the rn team to be doing. Namely providing access to the native apis through javascript, except that expo seems to provide much more features.
For me, what's holding me back from using expo is the additional complexity of yet another dependency and having to use more tooling (e.g. expo client).
I think right now it makes sense for us to be separate from React Native. Adding all of these libraries adds QA overhead and if Facebook doesn't use them internally it'd be hard for them to keep them up to date. In addition there are some other features we support that definitely don't make sense in core. For example we embed multiple versions of the React Native runtime in our app so that people can choose when they upgrade and we don't break old projects when we push a new version.
If you are not living in a city with plenty of developer jobs available then that's often not possible and you are stuck to the boring job "for money" scheme. Of course you can always relocate but this has its own downsides...
We as developers have privilege to work remotely. Don't excuse yourself saying "I need an office and people around". That's just not true, as you gain so huge amount of perks when you find a remote job it's madness if you don't even try it for a year or two.
If you really go crazy alone you can always find coworking space almost anywhere in the world.
Moreover, constantly look for opportunities. I recently heard very wise words that the best time to change your job is when you are perfectly happy with current one.
If you are not a web developer or DevOps it is very unlikely you have that privilege. I currently do ML/NLP, and my heart is really in embedded. Almost nobody is going to hire me to do either remotely.
There are way more important rules when it comes to passenger safety like e.g. driving according to the speed limit. I had a lot of taxi rides in my life and they definetly didn't feel safer than uber/lyft rides since, at least in my country, taxi drivers drive like lunatics.
