4 ms·
I agree, but that costs money for the company and time for the developer. Airbnb dropping react native due to a lack of qualified candidates that were articula
by david-cako 8y ago
I agree, but that costs money for the company and time for the developer.
Airbnb dropping react native due to a lack of qualified candidates that were articulate in both the native and javascript realm is a great example. Something can work flawlessly with the right conditions (for instance, developers that understand and can implement the path of least resistance across native and react), yet if its prohibitive to create those conditions you are back where you started.
If the dominant ideology among developers is that learning X language or technology costs more of their career than its worth, it dies out. Same goes for the company and their resources.
- macintux 8y agoI'm skeptical about extrapolating too much from a JavaScript example. That ecosystem looks nothing like the rest of the software development world. Erlang has been around in a niche role for >30 years and still going strong, even stronger now that Elixir has reinvigorated interest in the platform.
- david-cako 8y agoMy only point in that you should be as careful about creating problems building a team and adding ramp-up time to your product when you attempt to optimize. It's a decision that doesn't go away without lots of heartburn and having employees lose morale rewriting their own work.
- acehreli 8y ago> but that costs money for the company and time for the developer Quite the opposite: The new tool saves time and money. Airbnb example just shows that one should not jump on the newest thing on the market.
- blub 8y agoAccording to their own blog, they dropped react because it was a difficult to use piece of technology that was slowing them down and making it difficult to offer a top notch mobile experience. Yes, they also had difficulties hiring devs which know both native and react, but that's normal. Most mobile devs wouldn't touch react.