Telerik, Sencha and a few other companies sell RAD solutions or components for frameworks like Angular and co. There are also plenty of free JS toolkits
https://en.wikipedia.org/wiki/List_of_widget_toolkits#Based_...
Angular and co, they don't come with components like Delphi or Winforms, although they might have some official libraries(Material design,Bootstrap...) or widget collections that are separated from the frameworks.
But most of them will only deal with UI/data binding and it will be up to you to build components on top of that.
IMHO if your goal is to build desktop like apps and LOB on the web, don't bother with Angular,Vuejs,React and co, this is not the right abstraction. If you are looking for complex data grids widgets, have a look at the link I provided.
This is the exact same reasoning for charts. If you are looking for charts to use in your apps, don't use D3.js, use a library that actually comes with charts.
Is it the inter-component messaging? Integration? IDE support?
Vue and Angular are not directly comprable, Vue only deals with the V in MVC (View), where as Angular offers solutions for everything. vue + vue-router + vuex (or something else) would be a better comparison.
If you want a more guided/RAD approach maybe emberjs is more what you want to be looking at.
EmberJS's equivalent to Vue would be Glimmer[0], which theoretically can be used outside of Ember but might be hard, I've never tried it.
I did not call Vue a rendering engine. I stated that Ember's closest equivalent is Glimmer. I do think that statement is incorrect on it's face now that you've brought it up -- but I think that's because the closest thing would be ember's `View`, and not just Glimmer because the "View" abstraction is what Vue provides, and Ember's had `View`s long before Glimmer (they just worked slightly differently under the covers).
> The fact that it is lightweight and modular (...) does not make it worse
I did not ascribe a value judgement to Vue. I am a huge fan of Vue and use it a lot in my own projects and at previous jobs. I do not believe it's worse, but the simple fact is that Vue by itself is not comprable to Ember at all. They're different leagues of tools, Vue is a knife, Ember is a swiss army knife. Different problem domains that only sometimes overlap.
> Vue is also its own ecosystem same as Angular or Ember
Yes, Vue does have it's own ecosystem, but they are not the same as Angular or Ember.
> The ecosystem is in fact probably even bigger than any of them now
I don't agree with this. Angular 1 became the defacto frontend framework for corporations -- this spawns a LOT of ecosystem from people working on Angular everyday. Next was React, and Vue is just coming up NOW. I find it hard to believe that Vue has already gained the same amount of mind share as either Angular or React in terms of ecosystem.
Ember on the other hand has somehow managed to not land the lucrative corporation mindshare.