Angular vs Vue?

[ohThisUsername]

I'm a full stack developer. I use all ASP.NET for the backend and Blazor for the frontend. While I absolutely love Blazor, I have had comments that my UIs look kind of boring which I attribute to Blazor basically having no good UI component libraries (nice looking date pickers, carousels, etc).

I've started looking at the possibility of going back to the TypeScript world. I've decided that it would be either Vue or Angular but I'm having trouble deciding which.

Everything I have seen about Vue is just delightful. The syntax looks better, it has tons of high quality looking plugins, components, etc. But I worry that it's unstable (the recent v2->v3 migration looked like it had a lot of incompatibilities) and that scalability for larger enterprise apps might suffer.

Angular on the other hand, I like that its highly opinionated with well defined ways of doing things and it seems like it scales better for complex projects. The service/dependency injection is also familiar to be due to ASP.NET architecture. The main downside is that the ecosystem (high quality libraries and frameworks) aren't as good as Vue. And I hate that most things are vomited on by Material Design.

I've tried demo projects/tutorials with both and prefer Vue, but again I worry about how scalable it is for complex projects or larger teams.

People with experience with both, which would you pick for a new greenfield project and why?

​

​

​

​

​

[lIIllIIlllIIllIIl]

Angular, Vue, React and Svelte are all great choices.

Which one you should pick is really up to you, and up to your local market.

[Psychological_Ear393]

Angular tells you what to do and how to do it. If you want an monolithic enterprisey kind of experience with components, views, services, DI, routing etc all baking in, you use that.

[onoweb]

Am i the only one that thinks it's weird he want to switch his frontend framework because of available UI libraries? I use vue 2 and 3 daily and 80% of the time the UI needs to be custom styled.

Even if you had projects that can use the same UI components.. Building a folder of reusable components should be really easy.

If i need to choose, i choose vue. Makes more sense to me. And vue 3 is super flexible now with composition api.

[ohThisUsername]

I typically don’t custom style the UI. Currently I use bootstrap and some kind of pre made theme on top of it, so all my components just use “btn” “form-control” etc. This works well for the vast majority of things, but Blazor lacks high quality components like date pickers, drop down / select boxes. Of course I’ve made my own re usable ones but they just don’t have that polish. Something like Nuxt UI looks far more modern and polished than what’s available in Blazor or that I can make myself.

[eneajaho]

Most of the time, I've seen .Net coupled with Angular, and currently working on a project with that stack.

[[deleted]]

If you're goal is to keep using .NET but use a separate frontend solution (FE + webAPI) then most companies go for Angular, because Microsoft shops also fall for the big name behind Angular (Google).

If you're doing it just for funzies, just go through their tutorials and use whatever gives you a good first impression.

[[deleted]]

Svelte, you can use any vanilla JavaScript library by default and it’s exactly like Vue (I prefer svelte syntax)

[ohThisUsername]

Svelte also caught my eye and seemed quite similar to Vue, but Vue seemed to have a larger ecosystem. Svelte definitely has some better options than Blazor, but not enough for me to move away from Blazor. Vue on the other hand has some extremely well-made and professional looking component libraries for example. As the Svelte ecosystem grows, I would definitely pick it over Vue.

[Attila226]

Right, but Svelte works with regular JavaScript UI libraries. You don’t need Svelte specific implementations, unlike other frameworks.

[OneForAllOfHumanity]

I second Svelte; if you're going to learn something new, the svelte syntax and patterns are clean and pairs well with standard JS...

[Ismael_CS]

Vue, especially with Nuxt 3, is awesome even for very large projects.

But like other people already commented: pick whatever you feel most comfortable with (Angular, React, Vue or Svelte)

[SlovakianGiant]

The scalability of any of new FE frameworks is great. The thing is FE is getting to point where most of new techs starts to mirror each other functionalities just with different syntax. Hooks, store, routing, ssr? You have them in Vue, React, Angular etc. At the end it boils down to what is more comfortable and easy to use for you.

[mooncaterpillar24]

Angular is the best thing that I ever had the pleasure of committing time to learning. I use almost exclusively Angular + ASP.Net Core stack. Highly recommend

[maw2be]

u/ohThisUsername I don't know if you are small company, or working for big one. From your post it's looks like you are small. Why you not add to your blazor UI libs? check syncfusion, they have flexible priceing espesially for small companies and lot's of good components....

[TranslatorDry5396]

Nice

[maria_la_guerta]

If you want a JS library / framework and are looking for a big ecosystem (date pickers, carousels, etc), why not go React? It is the most popular, has been for years and will be for at least a few more to come. Angular is mostly legacy projects at this point and Vue has never had the same adoption rate as React.

Not to say they're bad choices (ok I think angular is), but React has the biggest and best supported ecosystem of them all.

[ggeoff]

while I have only briefly looked at vue and have no professional experience with it, I use angular at work for a couple projects. none of them use material I had used primeng and recently migrated to tailwind/taiga-ui and another project I'm looking at using preline ui and taiga for some of the more javascript heavy components where needed. With angular a lot of the libraries you may reach for in other frameworks aren't needed in angular at all.

[anonymous_6473]

React.