> Every React project that I've walked into has looked completely different from each other. Which, on its own, doesn't necessarily bug me as much as the attit

> Every React project that I've walked into has looked completely different from each other. Which, on its own, doesn't necessarily bug me as much as the attitude I've run in to. I've come in to a handful of React projects in the past 3 years, and each team says that "their" way is the "correct" way, and whatever I was doing elsewhere is just dumb/wrong/outdated/slow/bad/untestable, etc. "Oh, we don't do class-based here - that's so outdated!". "But... you have 85 class-based components already, and 4 functional ones..." "We're converting everything - class-based components are so hard to test" "How do you know? You don't have any tests around them at all" "Because it's so hard to test" "But you have no tests around the 4 functional ones -" "It's going to be easier once we convert all the legacy class -based components". I've done some Angular (versions 1-5) but mostly Vue these days. Angular was getting overbearing for me (especially on projects where I'm the only/primary js person), but I understand the appeal. A couple of colleagues have done Angular at big companies, and the structure (and extra layers) mapped very well to their existing way of thinking. I've shown one of those colleagues some standard Vue stuff - he 'gets' it, but thinks it's way too loose.