It specifically ranks chrome and chrome mobile seperately (both poorly), then talks about mobile development later in the article.

Well, were "later" is 80% of the article...

Including comparing mobile Safari to desktop Chrome, so I think its all part of one argument.

Amen. Probably just spending too much time on HN lately but I'm getting increasingly frustrated at the number of comments which are orthogonal or oblivious to the OP.

Yesterday's worst offender I think was PriceZombie where fully half the commenters didn't realize it was the Affiliate program not the Pricing API they got kicked off and so many "they could just scrape the data", "but no what about CFAA" back and forth.... And you read it and just shake your head :-(

The main issue is that it shouldn't have ranked the desktop platforms. It sounds like those are more for him, because the rankings were confusing to me.

Author:

In some ways, yes. But the ranking is really where I slide various browsers in terms of ease of getting an app working well, and I think it's important to note that I generally find desktop Chrome more troublesome than Mobile Safari.

The article is primarily about mobile Chrome vs mobile Safari, but the issue is only partially Android's fault. Chrome performs just as bad in JS and render benchmarks on desktop as it does on mobile, and it's memory leaks are present in both; but this matters less on desktop because powerful machines mask this for us.