I&#x27;m not sure that we should be doing this.<p>Yes, it stands to reason that if you take framework X, cut out a lot of functionality, remove some of the &quot;ugly&quot; code that addresses edge cases, then you end up with a similar, reduced framework which is smaller in file size.<p>But this is done at the cost of polluting the Javascript framework environment. The biggest problem right now is pollution, we&#x27;re all drinking from the fire hose of frameworks and someone needs to cut the supply so we can double-down on the good stuff and stop jumping from one framework to the next like a plastic bag caught in a strong breeze.<p>Preact is now a decision point for any developer who Googles &quot;react alternative&quot; and scans far enough through the search results. This isn&#x27;t right. This contributes to decision fatigue. It&#x27;s time to stop churning out new frameworks that are only marginally different from what&#x27;s already available.