So this guy is saying that if other vendors were able to implement their own engine on iOS, he'd no longer have to bother ensuring the work was compatible with the massively popular default browser on iOS?
The argument doesn't stand up that Safari is holding developers back because due to it's real world levels of usage by customers you'd still be unrealistic not to support it - that is unless people are planning a 90's style 'please use Google Chrome' on Safari, nice.
Basically the guy is lazy and wants to use some latest cool bleeding edge chrome feature and is annoyed he might have to do to some other work to support Safari.
I get the feeling this guy would be far more comfortable with a Google dominated Chrome monoculture of a Web.
The argument doesn't stand up that Safari is holding developers back because due to it's real world levels of usage by customers you'd still be unrealistic not to support it - that is unless people are planning a 90's style 'please use Google Chrome' on Safari, nice.
Basically the guy is lazy and wants to use some latest cool bleeding edge chrome feature and is annoyed he might have to do to some other work to support Safari.
I get the feeling this guy would be far more comfortable with a Google dominated Chrome monoculture of a Web.