He didn't say he absolutely knows that Chromium is phoning home "in some way shape or form". He just said that he doesn't believe it can be trusted not to. It's a legitimate concern that many people have, given Google's size and scope of influence. You may not share his concern, but that doesn't make his illegitimate.

If your objection is based on the fact that the project is using node, and there are also plenty of "phoning home" opportunities there, well I can see that too (npm/yarn being as they are), and I think it is something developers need to consider also. npm, Inc has perhaps a lot more power to abuse than many developers ever think about, but it is not near the scope of Google's. Facebook develop's yarn, which comes with its own set of concerns, as well, but you would not have to use yarn with NodeGUI (assuming you can, I haven't looked).

Assuming your objections were based on node having it's own privacy concerns, I guess rather than labeling the discussion of Google/Chromium privacy concerns as "FUD/BS privacy concerns about Electron or anything from Google", I would have just pointed out the concerns with node.

EDIT: oh, and of course, since V8 is Chromium's javascript engine, and that's what node uses, well maybe NodeGUI dev just didn't think about that. :-D