The fastest UI library and the team behindit Firstly, what isInferno?
Performance issues were especially highlighted in the mobile space, and in the two years since, there hasn’t been much improvement. While library footprints shrank, some users still waited ~5 seconds for a 2MB to parse and load.
Many developers, including Dominic, grew increasingly frustrated and desperate for an answer. It was obvious that libraries needed to diet down and start caring about performance. Experiencing an application from a laptop was never, ever synonymous with mobile experience; especially in emerging markets.
Now, as a result of many tests & a growing list of contributors, Inferno proves that it is possible to be fast on mobile. Much of this success is a direct result of hoisting Time to Parse (‘TTP’), First Meaningful Paint (‘FMP’), and Time to Interactive (‘TTI’) as first-class priorities, among others.
Inferno’s power, reach, and usage exploded as its list of contributors increased ― a prime example of OSS a it’s best. The project, which once started as a mere experiment, now has a full core team, actively committing thousands of hours into building and polishing this beast known as Inferno .What the project has achieved?
Inferno is actively used at companies such as:Microsoft The Grid Uber Yahoo Evite.com
Inferno 1.0 is really well written. It’s how I would’ve written React. I’d recommend reading its source to learn.
― React core team member at FacebookExplain the path goingforward?
In 2017 Inferno will focus on continuously improving its core functions, addressing bugs as quickly as possible and providing support and guidance to the community. Effort will be placed into adapting new libraries to expand Inferno’s reach and modularity for a wide range of use cases. To date a range of modules have been ported, but with additional effort from the community we intend on expanding this further. Some of the focus we’ve planned this year includes:
Internal Optimizations:Improving VDOM normalization process Optimizing internal functions Refactoring our mono-repo using Lerna Improve typings Planned moduleports Material-UI General ideas Improve SSR and streaming
Our roadmap is 100% community driven and we are constantly looking to improve the library to maximize developer satisfaction. If you have any idea for an enhancement we encourage you to become involved by contributing or at minimum hop on Slack or post a Github Issue for consideration. If we don’t hear from our community, we won’t know what direction it needs to run in.Our Team