I think it was a great article. A lot of people go in with the assumptions that the author has. At my last position we used Cordova. Like you, I was against it

I think it was a great article. A lot of people go in with the assumptions that the author has. At my last position we used Cordova. Like you, I was against it from the beginning because it is so unlike native. Yet many are under the impression that using Cordova means writing half the amount of code and/or taking half the amount of time that it would take to write separate iOS and Android apps. They think it's possible for reasons specified in this article (generally: that experiences are native-like and development is not harder than native); namely: - that it can be like native; I regularly heard from management "What is so difficult about CSS? Why is it taking so long to build widget X?" - that there is no reason why it can't be fast; I regularly heard from management "iPhones have >1ghz processors after all -- why can't it be faster?!" - that the plugin ecosystem is bad -- "Why can't we just do X? Why do we have to build this?" I agree with your criticisms as well. The lack of documentation, plugins, breaking between releases, and general help is surely lacking. But this is by no means a "bad article."