Facebook releases so fast. So when something is brand new and it's already not using the latest, I feel afraid.
The example project doesn't use the import syntax, it's using require, and feels like it's coming from ECMA5 in a brand new video. I just worry, can they keep up? Facebook releases breaking changes often so it's a valid concern.
I applaud effort. I just feel there's some glaring gaps that make alarms go off. I'm sharing those. I know this looks fantastic, but that's when I start checking for a venire. And when I do, those smells popped up.
I think "irrelevant" is a poor choice of words here.
It is VERY relevant that there is a workaround. Additionally, it's kind of unfair to point at 1 bug (that has a workaround) and judge an entire system on it.
That's the attraction to phonegap, but what happens when your "nail" changes? Your client might ask for a small feature that the API doesn't support, which renders your entire solution useless, or cumbersome.
One of the points in the article is that the second you want something phonegap doesn't provide, you're stuck back-peddling, or over-engineering your fix. We've already come across such a situation with one of our upcoming projects that requires camera overlays.
Ultimately, it's important to compare options, whether they be frameworks, native, or toolchains. They're all avenues that need to stand their ground against other avenues.