Honestly, it doesn't reflect my experiences. I come from a C++/C#/.NET/WPF background. For the last 3 years i worked on web applications. Debugging Chrome dev

Honestly, it doesn't reflect my experiences. I come from a C++/C#/.NET/WPF background. For the last 3 years i worked on web applications. Debugging Chrome devtools can see into every aspect of the app at any time down to a single frame. That extends to the server if you're using Node. With Webpack code is written live, parts you edit change, the rest stays put. State management like Redux makes the apps flow inspectable. Debugging has never been more powerful and easy to handle. Frontend The key is picking the right foundation for your project. React/Vue are the fastest MV systems i have worked with. To get comparable results in XAML we'd write 10 times as much code that probably even performs worse. Yes it can crash and burn some day, but we're so close to web components, it's not going to sting like the ng1 debacle. Data JSON has been invaluable. I see more and more C++ devs rely on it (nlohmann/json). I won't go into benefits, this one is obvious. Types aren't a problem. Most people do fine without them. If you need types you have Flow. The point is, if you barely know your way around, haven't worked with ES6 and modules, the eco system and npm are foreign ground, you will have a bad time. But if can pick the right pieces, chances are you will have a blast. This year has been somewhat different in that i had to introduce grumpy C++/C# devs, that have been re-tasked because their stack is falling out of favours, to JS. In the beginning they're all a bit like you, they have done some "research" cherrypicking bits and pieces that fit their "JS is a toy" & "lib fatigue" agenda. One week in they've made their first experiences and start to sense the possibilities. Two weeks in they start to grasp the idea that worlds biggest dev community is behind JS-literally whatever it is they seek is on npm. A month or so and they're happily building apps.