You actually quoted one of my points, then reacted to another.
A very bad first impression to make, I’m sure you’ll agree.
As for the “especially when it could be interpreted as the makers of a high-performance language with strong static guarantees having so little faith in said principles as to write native applications in NW.js” that you seem to be reacting to, here’s what I worry about people reading into it:
Rust is supposed to be chasing C and C++ when it comes to efficiency, yet these people seem to see no problem in reinventing and/or breaking built in functionality of the browser (something which began as a cross-referencing document viewer) in its inherently less-efficient internal scriping language.
“Everyone knows what a hog Firefox is. This is just more proof that, be it incompetence or lack of will, Mozilla chronically doesn’t practice what they claim to preach.”
(As you might have guessed, that last one isn’t intended to be a rational argument but, rather, an impression that’s difficult to change once established.)
…and, since the ecosystem is centred around Cargo and crates.io, that can then make it more difficult to convince people coming from languages like C and C++ to trust Cargo to handle dependencies.
P.S. Sorry for being so tactless in my initial post.