anyone care to share their opinion on using angular over vue?

I'm going to have a project come up soon that's driven heavily by multiple api backend services and I'm leaning heavily towards vue due to the extensibility and the small learning curve.

Anecdotal stuff:

Between the two, I've not yet seen a large VUE project.

A small app... can't imagine it would be a big deal, but bigger app... not so sure.

Unless you do some Frontend in Frontend stuff like ikea using different frameworks, angular is very extendible and gives you everything you could imagine already.

Vie can be a bit loosely and become a mish mash of things. Even if the upgrade process can be annoying, it’s mostly very clear and doable, there rarely are headaches on upgrades - unless you did something non-standard.

@N00bPancakes this is large in product but small in service.

meaning, I plan on making a user and account management vue app, and another one for ticket management. there's probably about 10 more, but they all relate together for a single product.

they'll also share alot of convenient code together(data tables, charts, etc), but those can be actively maintained as npm packages from our internal repos.

my goal is to empower the dev minded ops engineers in my company to build their own tools, but give them a scaffold to build on. I kind of feel like vue can give them that since it has the html/css familiarity but will push them to learn js/es6.

@bagfox that nonstandard thing is a bit daunting.

The company I work for uses nonstandard as a spice on everything they do.

I work with another team that does angular and holy shit they screwed the pooch on that. I'm leaning away from angular because I secretly don't want any of them to touch this thing before it's established.

their method of development reminds me of that scene in Borat when he's breaking all that shit in the antique store. funny yes, but not if you're the store owner.

@sariel literally all of our angular devs come from a company like that. We try to stay as standard as possible, even if we dislike it sometimes.

So far, it worked great to introduce new „devs“, speaking cheap students who work on the annoying tickets

In your case, I would definitely go with Angular, since Angular is very extensible, forces good practices on you and doesn’t get muddled as easily when the scope of the project gets out of hand.

I was part of a big frontend project done with Vue not too long ago, and I can tell Vue is very fine and neat only until a point, where things just seem to get too large for Vue, if you get what I mean. I like Vue, but in my experience with frontend I’d advice to go with Angular when the overall scope becomes larger than a certain threshold (hard to pinpoint what that threshold is, exactly) or if there is a danger of it growing as time goes by, and stick to Vue or even React when it’s smaller, choice depending on the requirements.

Tl;dr: I have a hard time justifying Vue for large projects. Go with Angular. That’s my 2 cents.

// EDIT: I read your second to last comment (properly) - Vue could work in that case, but there’s no real advantage over Angular either, as far as my morning brain can tell

Given what you said, Vue (v3) would be the best choice; however, if it's an enterprise level app or a massive system, then Angular would be better.

@ostream You know you can use Single File Components in Angular, right?

@ostream

Agreed. Sometimes you gotta pick out what you think will work for everyone... even if not the ideal.