[codeflo]

Everyone's experience is different here, but I've grown to hate these all-encompassing frameworks -- somehow I always run into their limits. As far as I understand, Angular has its own module system, its own dependency injection, its own test framework. If you have any special requirements for any of those, you usually can't rely on the vast JavaScript ecosystem because Angular doesn't play well with many common JavaScript techniques. React also has a precompile step with JSX, but that's simple syntactic sugar, and besides that, React is really just a well-behaved library with a surprisingly small API surface. It doesn't try to do everything and it plays well with non-React libraries, at least in my limited experience. I usually find that in any context, taking such a mix-and-match approach is a lot more flexible in the long run than using a large framework.

[jf22]

Can you describe what limits you run into?

[boubiyeah]

They work best if your team has low standards and just settle with whatever the framework has choosen for you. I'm not surprised it's fine for many.

[nickserv]

I'm not sure I would consider uniformity "low" standards.

It's quite useful when there are multiple smallish projects, for example your typical web agency.

Also useful when you have one or two experienced programmers and a few less experienced ones: makes it easier to review the code.

That said for a highly custom application, especially one you're betting the company on, and need full control, a lower level approach can be beneficial.

Not limited to Angular vs Vue.js, the same applies to Django and Flask for example.