Why We Moved to React
No matter how I try to accept it, it is a really bad idea to embed views into business logic.  You have no clear separation of concerns and this can create a lot of headaches as the sophistication of the application grows.  Instacart is a great product, but it has a lot of room to grow still.  What happens when you get into some deeper aspects of UX?  I presume you do your own UX research and these highly segmented views are going to be a pain to manage.<p>You&#x27;ll also need to worry about how you run BDD tests for specifications and scenarios. How can this be achieved in React as you write test suites for user stories and non-UI acceptance tests?  How will this impact your continuous delivery&#x2F;integration systems as well? You&#x27;ll have to rewrite all your test suites into Jest, right?<p>There are architectural trade-offs for sure. Can you definitely say you&#x27;ve performed a thorough analysis before making this decision?  There&#x27;s a difference between having a clear strategy to move from one tech to another and knowing that the migration will not just bury you into a deeper whole than the one you think you&#x27;re escaping.<p><a href="http:&#x2F;&#x2F;aurelia.io&#x2F;" rel="nofollow">http:&#x2F;&#x2F;aurelia.io&#x2F;</a> is based on webcomponents (MVVM), ES6, and current web standards. It&#x27;s amazingly simple and good architects can use their own structural patterns to create code that can actually scale with the product.  DDD and BDD methodologies mesh perfectly into the development workflow, especially with Agile product development.<p>I wish you well, but I really think React is a short sell with dire consequences.