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 ?
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).
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...
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.
> As an added annoyance, which is specific to App Engine but a result of using the JVM, it's impossible to specify JAVA_OPTS, so any of the -X flags, without switching to the Flexible environment
I haven't used App Engine either but I suspect that the flexible environment is more expensive.
