You can see more about this in the library comparison below. React-Lite. inferno is less popular than preact. Inferno is 8kb, it's smaller than the Mithril re-write and is on par with Preact in terms of parse performance. Here's a comparison of the Lighthouse scrores of the React vs Preact versions. There is one last thing to make RHL work. The personal project Inferno flourished into a whole community, which created a serious competitor to React. Preact offers several other features nifty features such as the rendering of both props and states, linked state, and the utilization of ‘class’ instead of className. Use Preact to build parts of an app without complex integration. Inferno differs in that it offers some additional features that React or Preact don't have (at the expense of some file size): Tiny in size; in fact, only 8kb min+gzip. I think you may have looked at the older Inferno codebase, as the current one is very slim and readable. The conversion to these frameworks turned out to be nothing but easy. Here's a chart showing npm downloads for Preact, Inferno and Svelte over the past year: Like Inferno, Preact has many similarities with React. For both Preact and Inferno the conversion from React is touted be very simplistic — simply alias React and React-dom in your bundler to (Preact or Inferno)-compact, and boom, your bundle just got 30kb smaller. In our root component we need to: Preact's tiny footprint means you can take the powerful Virtual DOM Component paradigm to new places it couldn't otherwise go. will you be competing with Facebook in any way, or is there a chance you'll sell to someone who is), this could be the dealbreaker for React Inferno's debugger is on average, 4x faster – fixing lots of the issues with slow, laggy interfaces when developers are debugging. Inferno is larger in size, 8kb vs 3kb gzip. Preact and inferno will ignore the changes if we use it. Inferno is MIT-licensed and doesn't have a 'patent rider'. Differences from Preact. The sole reason to create this library was to introduce the lighter version of React JS. Embed Preact into a widget and apply the same tools and techniques that you would to build a full app. However, someone with a lower end Android phone may very well appreciate the improved performance of Preact over React. Here’s a look at a typical Preact component taken from the documentation: If you’re familiar with React, you may notice something different — the inclusion of “h” in the import statement. It parses and evaluates as quickly as anything in the browser (almost the same as that of Preact). Again, someone using a top tier Apple or Android phone is not really going to notice these differences. If React and Inferno were completely equal, and depending on what the endgame strategy is for your project (i.e. Unlike Inferno and Preact, there is no compatibility package require. 3. Compare inferno and preact's popularity and activity. This means that Preact should parse faster than Inferno – if only slightly. Categories: MVC Frameworks and Libraries.