The reason is because the WebKit engine on iOS is heavily optimized for battery life and can make use of private APIs that further that goal.
Safari and Chrome are essentially the same engine under the hood, the web wouldn't "feel" better if you had one over the other.
I'd add security too here. Also, if they allow native Chrome on iOS, Google domination in web standards would be complete and irreversible.
The reason is because the WebKit engine on iOS is heavily optimized for battery life and can make use of private APIs that further that goal.
Safari and Chrome are essentially the same engine under the hood, the web wouldn't "feel" better if you had one over the other.