> Put a JS dev and a C++ dev of equal experience against each other and the JS dev will have fewer bugs. At the most basic, the JS dev would have all the same l

> Put a JS dev and a C++ dev of equal experience against each other and the JS dev will have fewer bugs. At the most basic, the JS dev would have all the same logic bugs as the C++ dev, but subtracting the memory bugs from the JS bug count would itself be enough to prove my point. On the other hand the C++ developer can use boost and Qt libraries to have a wide range of well tested, well implemented components that implement a wide range of things, without having to sift in npm for hundreds of low quality abandoned modules. So IN TOTAL, your point is far from proven. > As to keyboard navigation, that is entirely up to the devs to implement No. Toolkits for example implement decent tabbing. The qt designer offers a GUI to decide the tab order. And assigning shortcuts is even easier. If you go and use kdelibs you get support to completely customize every single shortcut from the control panel, or from your own application. Oh by the way with Qt you also get support to find in which directory to save settings, data, and so on. Which is not so trivial because all the defaults can be overridden by specific env vars. You can either use C++ and a toolkit that does all this stuff, or JS and reimplement everything every time. Now you're arguing that reimplementing every time is faster. It's an opinion but I don't think it's as obvious as you think it is.