&gt;<i>I understand building a faster React, an easier to use React (forms are a nightmare), but a smaller React? We are talking about saving on the order of 30kb. This doesn&#x27;t even matter on mobile. Can anyone give me a compelling use case?</i><p>Less code can also mean its easier to understand and has pruned the legacy&#x2F;redundant parts (being ES2015 only).<p>And being able to read the whole code of your framework in one sitting, and understand it, is great.<p>Besides, it&#x27;s not like &quot;as little code as possible&quot; is their ONLY goal. They&#x27;re not merely building a drop-in React replacement with less code. The reference to &quot;Mithril&quot; looks like they&#x27;ll also investigate their own APIs and ways of hooking components etc, which will be similar in concept but different than React&#x27;s exact APIs -- they already dropped the non-stateless components APIs.<p>[addition] Regarding the &quot;order of 30kb savings&quot;. Here&#x27;s an excerpt from their site: &quot;The React-based demo was 1.8mb of JavaScript. This demo, using exactly the same code and with the same functionality, is 60kb.&quot;.