> reducing their issues to one thing Not at all, I focused on the one thing that was mentioned as the most significant reason for team frustration with react n

> reducing their issues to one thing Not at all, I focused on the one thing that was mentioned as the most significant reason for team frustration with react native. > I don't want to come in too hot No worries > it's increasingly clear you are pretty fresh in your career I was thinking the same thing about you, no offense. > but taking this kind of negative view Not sure what you found negative about my view. Teams and individuals make mistakes and misjudgments. That is part of life. If you read my comments I said that removing RN was probably the right thing to do by the time it happened. This is often the case with bad technological decisions in startups and is rational because of sunk cost. > many_ cases and orgs where it is not a good fit This is why I cite architecture. With react or react-native you really need to know where the data is coming from and how the data will flow through the application. I'm arguing that the architect should have had a plan for how this would work before introducing react native into the app. Airbnb has done a lot of great react-native work, so I know the issue isn't technical competency, but the linting rules Airbnb popularized suggest a very trees-oriented (not forest oriented) perspective on tech, which is the kind of perspective that makes the above kind of mistake.