Also a C++ developer, I completely agree. If frameworks repeatedly have lifetimes of a year, that suggests to me that a) nobody really knows what they are doing, b) there is no way to do it well in JavaScript, or c) maybe the problem is that a document description language (HTML/DOM) is unsuited for the kinds of things we want to do on our websites. You can pick pretty much any of a number of UI toolkits for inspiration, they all look pretty much the same. It's not like UI is a completely unsolved problem. It's not even a partially unsolved problem.
I'd be interested to know what the problem actually is, because I certainly don't want to have anything to do with the mess until someone comes up with something solid.
I had the luck to ride the first .com wave in the 2000's, that is where I got my web skills.
Then after almost 10 year being busy with server side coding and native UIs, got back to it in around 2009.
Eventually got back to native UIs in 2013. Really happy to be back in native UI land.
It is just plain chaotic the tools aren't up to the tooling level we had already in the 90's with RAD languages like VB, Delphi and C++ Builder.
Using XAML + Blend, Android Layouts or iOS Storyboards is just plain nirvana compared with the chaos of making <div/> + CSS + JavaScript pretend they are native UI widgets in a portable way across multiple browsers.
Also having to worry about the build tool of the day is just crazy (npm + bower + yeoman + whatever else is required).
I'd be interested to know what the problem actually is, because I certainly don't want to have anything to do with the mess until someone comes up with something solid.