When I switched from Ember to react what I missed the most was the two ways binding, the computed properties and the router. From dabbling in Vue.js it seems to have incorporated the best of both worlds. I read over some of the technical implementation and it seems pretty sane. It seems too good to be true and I am honestly wondering what is the catch. Everything I have read about vue has been very positive so far. I am curious what are some of the cons of using vue
I totally agree with you. I don't think Uber would have a monopoly on self driving cars. In terms of the tech, they are definitely not ahead of e.g. Google. According to this TechCrunch article [1] their self driving cars require human intervention every minute.
Lyft's valuation is still 1/10th of Uber's. I don't think we need to worry too much about Uber going under anytime in the near future. Uber still has another 10B in the bank. As a consumer, I am supporting Lyft so that they might live another day to keep the competition going
It is a broken relationship that would be hard to fix. Uber doesn't even try to hide its intention to get rid of the drivers once it has its self driving cars fully deployed
To be fair, other CEOs are not constantly acting like a jerk to everyone. Maybe Travis will be more likable if he follows the footsteps of Bill Gates and Mark Zuckerberg and pledge to give the majority of his wealth.
Uber pool is just a terrible experience in many levels
1. Many drivers think they make less if the passengers are using Uber pool. I am not sure if this is true or if they are confused. However, when they find out I am using pool they instantly turn passive aggressive and start complaining how they make nothing on a pool ride. They make me feel as if I am taking advantage of them.
2. Uber also tries to pack the car these days. A lot of times, it is probably much faster taking public transit than using pool. One time, my pool ride was just going around picking up people and 15 minutes later I was exactly a block from where I started. I got off the ride and Uber has the balls to charged me $10 for "cancelling". Decided to quit Uber on that very day. Will only ride public transit or Lyft these days
React Navigation seems to be the framework that is endorsed by the react native team. However, Airbnb's React Native Navigation library seems to be more proven since they had been using it in production. I am wondering if anyone know what are the benefits of using React Native Navigation vs React Navigation
My team is in the process of swapping out the navigation stack in one of our apps (we are going with the one from wix for now). Something you might want to consider is the following (copy pasted from my other comment):
"The problem with all the JS based navigation stacks for React Native (react-native-router-flux, react-router, React Navigation) that I have tried is that if you need to have a back stack, they keep the previous scene in memory. i.e if you look at the 3D view hierarchy in XCode you will see the screen prior to the one you pushed."
The docs for airbnb's new navigation stack says the following:
"React Native Navigation by Wix engineering is an alternative library that uses "Native" navigation components of each platform, and has been around longer than Native Navigation. If you need a stable / production-ready navigation library today that uses native platform based navigation components, we recommend you check this library out."
They also claim they are not using this library in their main app yet.
I'll be writing up a blog post about my experiences with the wix nav stack migration once we get our app out.
It's a shame the situation around navigation stacks with React Native is so confusing right now.
React Navigation seems to be the framework that is endorsed by the react native team.
The React Native team respects Airbnb's work here a lot as well. I think we will end up with an "official recommendation" that says each of react-navigation and native-navigation is better for a different set of use cases. It's probably too early to figure out precisely what the line is.
Roughly, react-navigation is more customizable, native-navigation works better for native <-> RN transitions, and they should each be easier to use than the "first generation" of navigation solutions like Navigator / NavigatorIOS / NavigationExperimental.
I also been testing navigator and also react navigation. Original navigator need more code compare to react navigation .. Now i'm unsure which one to moved on while few weeks ago people arguing react navigation is better.. I also have seen the wix version but i haven't done some testing how it work.
