未加星标

Introducing Inferno 1.0

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二03 | 时间 2017 | 作者 红领巾 ] 0人收藏点击收藏

Introducing Inferno 1.0
The fastest UI library and the team behindit Firstly, what isInferno?

Inferno is a lightweight, blazingly-fast, and mobile-efficient javascript library. Derived from React, Inferno’s architecture & lifecycles will feel familiar, but its computational engines render it a totally different beast. Inferno stands as one of the fastest frameworks available and has been developed from the onset with a focus on performance while maintaining React compatibility.

Humble Beginnings

Nearly two years ago, the JavaScript world was filled with many debates about front-end performance and assertions that “the web is as fast as it’s over going to be”; so, naturally, Dominic Gannaway began to experiment.

Admittedly, developers did struggle to write highly performant applications using any of the UI libraries or frameworks available during this time. To no fault of their own, these libraries just didn’t have the same technologies or were able to leverage modern improvements to JavaScript engines. And so, many developers turned to “vanilla” JavaScript, which did the job, but quickly became messy & hard to maintain as their apps grew.

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.

This was possible because the Inferno team worked closely with the TypeScript and V8 teams, so that Inferno’s compiled core leverages and works with the modern V8 engine. As a result, Inferno is (the most) highly optimized JavaScript UI library currently available.

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?

In a short period of time Inferno grew from around 150 Github stars at the start of the year, to around 7300 by the end of the year, 15 NPM downloads to 15k a month and 300k downloads from the CDN. It’s consistently rated one of the fastest JavaScript UI library in all independent benchmarks and has been benchmarked internally (used for metrics against internal projects) at Google, Facebook, Microsoft and Yahoo.

Inferno is actively used at companies such as:

Microsoft The Grid Uber Yahoo Evite.com

Inferno has also had many phenomenal kudos and positive reviews from across the JavaScript community. Although recognition is not our driving force, nor are stars or downloads, we love hearing that the library is going in the right direction:

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 Facebook

Explain 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

The Inferno team is comprised of dedicated individuals who strive to build the best possible framework. The following members are core contributors, who have supported the project with a range of competencies:

Dominic Gannaway (Community Founder) ― An experienced software engineer/architect with a strong focus on web technologies, open-source, leading agile teams and writing elegant JavaScript code. He has contributed to many open-source projects and is soon to join Facebook’s React team in London. Sampo Kivisto (Core Contributor) @havunen ― Sampo is a Finnish software developer and one of the first contributors to Inferno and has worked closely with Dominic throughout the project’s evolution. He currently working at Visma Solutions Oy. Luke Sheard (Core Contributor) ― Luke is a British application developer based in London, UK. He has a keen interest in web technology, open source and developer experience. He’s contributed to various React projects before focusing on Inferno and aims to improve developer experience. Luke Edwards (Core Contributor) ― Luke Edwards is a freelance full-stack (front-end heavy) developer and web designer. He’s obsessed with performance and believes that open-source should be an integral part of every developer’s career. Luke spends his spare time perfecting Fly.js, constructing front-end boilerplate starters, and building new packages for Elixir lang. David Di Biase (Community & Website Support) ― David is a full-stack software developer based out of Toronto, Canada. He has grown and managed his team of designers and developers at Pilot Interactive for 8 years. He has contributed by managing the Inferno website, docs and general community maintenance tasks. Ryan Megidov (Core Contributor) @nightwolfz ― Ryan has been doing front-end and back-end development for more than 10 years. He loves following tech trends, using the best tools for the job, and experimenting with various new technologies. He stresses that he doesn’t wear socks and sandals at the same time, but the core team doesn’t believe him. Dan Tocchini (Community Support) @d4 ― Dan is the founder of The Grid, a software company that aims to solve “the website problem using artificial intelligence”. He has contributed to a number of open-source projects including but not limited to GSS (an efficient and elegant Cassowary implementation in JS).

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

主题: JavaScriptJavaReactFacebookGitCDNUberSlackTI
分页:12
转载请注明
本文标题:Introducing Inferno 1.0
本站链接:http://www.codesec.net/view/520376.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(54)