Entrusting high-level architectural technology decisions to engineers who have limited experience in a domain often leads to bikeshedding and bad decisions — and this showed in the side project we did. We are a team of 4 engineers building Clef, but since we regularly maintain code across 5 platforms (iOS, Android, backend Python, client JavaScript, and our WordPress plugin), only two of our engineers have really worked on our React application. By the end of working on the side project as a team, we’d saddled ourselves with a set of tools which often proved unstable and got in the way of getting our work done.
Choosing Ember over React in 2016
Jesse Pollak
52225

Do not engineers behind a highly opinionated framework also suffer from their own set of decision problems? Biased decisions to validate their initial approaches and commitments; slow or too fast adoption of improved or new design patterns. Why not subsidize some of the decision fatigue with the development community as whole? I’m doing that now and it appears the clear winner is the beautifully unopinionated and composable React library loosely coupled with Redux. The beauty is in having the control and flexibility to make your own decisions and to not be penalized when you change them. I’ve built apps with both Ember and Angular; Let me rephrase that, I was wed to them both and the divorce was brutal. I prefer being single and dating, and React and Redux are the best friends with benefits you could ask for.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.