Kinda is a war unless you're working solo, cause you're gonna get forced to use something or another. When I tried a few solo web projects instead of just being a backend guy, I picked up React on my own because it was the only thing that makes sense. The page does what the code says. And that was after trying other things.

Now I gotta occasionally use Angular, and it's boilerplate hell. Adding one button involves editing 30 classes and files even if you don't use templates. I took a course at work where even the instructor got confused adding a button. Why would anyone ever use this besides Google, or do they even use it?

▲ Tokumei-no-hito 4 days ago | parent [-]

in the world of frameworks it's obvious that

html in your JS > JS in your html.

angular is a mess. it's the java of web frameworks. if you want up be enterprise(tm) go for it. I’m convinced it's only a thing because it gives people job security since nobody else chooses to touch it.

	▲	Anamon 21 hours ago \| parent \| next [-]
		I don't know what you guys are doing with your Angular buttons, or if you haven't looked at it since AngularJS (which I never used, so I don't know what it took there). Adding a button to Angular is just adding a <button> to your template. If you want to use Angular Material, that's one additional import in your component's code file, and one additional attribute for that template's <button> element. `import {MatButtonModule} from '@angular/material/button'; <button matButton (click)="onClick()">Click me!</button>` That's it. If your instructor got confused trying to achieve that, maybe that's why you were left with this weird impression of how verbose and complicated Angular is. Just at least have a look at the documentation or tutorial before spreading fibs like that.
	▲	frollogaston 4 days ago \| parent \| prev [-]
		There was also the actual Java of web frameworks, GWT