I know, right? Friendly, bearded, probably lives on the west coast and uses a Mac. Ugh. Can't wait for new technology to make these pathetic hipster devs hired by Microsoft for their abject lack of competence to go out of work.
Sort of the developer version of "Nick Burns, Your company's computer guy"
But you're both wrong, and I know it's obvious to everyone reading this comment but I'm spelling it out for you and OP specifically because nobody ever calls anyone out correctly.
There is a nuance to technology; it's not black and white and leaping to the extremes is not helping.
Is Javascript a "good" language by the classical definition of "good", well, no, not really.. but it's "good enough" for enough stuff and the ecosystem is the healthy part of it.
My point is (if I'm trying to make one), making things natively is certainly better for users RE: desktop software. So if you care more about your users time and their resources than you do your own development time then it makes sense to do it in a native language. (Not ASM, that's facetious)
The question invariably becomes: "Yeah, JS is /classically/ a bad language, mostly known by people who aren't formally qualified programmers who understand systems"
vs.
"Yeah, but can you imagine making something cross platform in C++ in 2018! talk about foot guns!"
There is middle ground here, but unless we can talk about it professionally and with charity to the "other side" then we'll never get anywhere.