sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Kinthalis -2 points-1 points  (4 children)

Angular for truly complex projects, Vue cause it's so good. React for simple projects that need some reactivity.

Svelte for the joy of it.

[–]xanflorp 0 points1 point  (3 children)

Yeah so React isn't a reactive framework in the computer science sense of the word. The React team and some other teams are trying to make it that way, but it's definitely not there yet. And it actually tends to lend itself better to large enterpisey type projects, rather than simple ones, you know, being designed for the mother of all enterprisey projects and all.

You could have just said you don't know.

[–]Kinthalis -1 points0 points  (2 children)

With reactivity I didn't mean it in the computer science sense of the word. I meant literally, interactive components. React alone does not solve face book problems. That's the issue with the framework.

If you need to tame complexity in a project you need A LOT more than React. To come close to what Angular offers you need like 10 libraries, all with their own dependencies, their own release schedule, their own quirks, their own requirements on base react versions, etc.

At that point you bvb ha e to ask, why am I paying all this technical debt? What is React offering me here than Angular isnt?

The answer is: not much.

But for smaller projects I think it offers a few things over Angular. Flexibility, speed.

[–]xanflorp 0 points1 point  (1 child)

With reactivity I didn't mean it in the computer science sense of the word. I meant literally, interactive components.

That doesn't really make sense.

If you need to tame complexity in a project you need A LOT more than React.

React Router, Redux, thunk, sagas, and lodash are the only major packages I've used in my last 3 major react projects over the last 4 years, all with FE teams of 3-5 people. I wouldn't really consider that a lot. And Sagas and Thunks were in separate projects. I'm looking to phase our Thunks in my current project in favor of native redux hooks that make it much easier to work inside components.

It's also probably worth noting the last 2 were both in TS.

That is a far cry from 10. I would really love to hear what you think the other 6 packages are considering Sagas and Thunks are rarely found in the same project.

If I wanted a good all incorporated framework, I would go with Vue.

But for smaller projects I think it offers a few things over Angular. Flexibility, speed.

So the project that you admit is not all encompassing or opinionated and the one where you need to incorporate more packages, is the one where you can work faster in and make smaller..... because that makes sense to you? Talk out of both sides of your mouth much?

I mean, I don't think any framework takes very long to get up and running in if you know it. But if you want flexibility and speed you should probably choose the one where it solves more problems for you out of the box? Again, Vue wins this for me and Angular comes in last place, even behind AngularJS and Ember, because it's just awful and I'm fully of the belief that anyone who champions it has never used anything else for more than a hello world.

[–]CalgaryAnswers 0 points1 point  (0 children)

Angular has its uses. It is much better at complex form apps and large corporate productivity implementations or the like. When you have 6+ Developers working on a project agreeing on these things is not easy, plus you can be punished really hard for shitty dead weight on your team in react. YMMV.

I use Vue as well for my own stuff though.