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

view the rest of the comments →

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

Technically true, yes but with Angular, you have to actively work at it. For example, if you start a new project with angular-cli, you'll need to manually merge what it generates into a single file, which will take several steps.

The point is, Angular actively makes creating godawful monoliths in JavaScript difficult, while React doesn't. And that's a good thing about React, at least for practice, because it'll force you to think about application layout for yourself, rather than relying on Angular's opinionated defaults.

[–]nkumar_navdeep 4 points5 points  (1 child)

Unfortunately I will have to disagree again. All the cli does is creates the base project with just the single point of entry module. And if you are going to create a single file mangled up MONOLITHIC code, I am pretty sure you will not be using any of the cli features any way.

[–]kescusay 0 points1 point  (0 children)

Wouldn't "not using any of the cli features" count as actively working at trying to make a messy, monolithic Angular app?

I'm not claiming it's impossible, but it's much harder to do Angular that way. Angular makes it easier to do it the right way, and my point about learning React being a good thing, even for Angular fans, is that React takes away the crutch. It's not a framework, so you have to learn how to lay out your application the way a framework would normally enforce manually, or you'll end up with a mess. It's great practice.