To quote the only comment from the last time this article was posted:

> It seems the entire blog post is based on a misunderstanding of React Native's goals.

Which is true, per the blog:

> There will nearly always be some level of customization required, Developers and designers will nearly always need to have direct knowledge of each platform target.

Which is exactly why React Native has separate controls on iOS and Android when necessary

I like to think of React components as interfaces. I'm saying that this component is capable of handling these actions, and displaying these things. On different platforms the exact behavior is expected to change, but I can trust that my UserStatus component always accepts a users status property, always displays it and perhaps manages modifying it. I can trust that my LogCard component will always be a container for a log using the same actions.

In that way I'm free to modify the implementation of the component to match the platform and can still share the component across platforms.

The React team has already stated they aren't attempting to Write-Once-Run-Anywhere, they are establishing patterns for learning once write anywhere.