trueadm

We do have a link to a live demo. It's the Lexical Playground:

https://lexical-playground.vercel.app/

Happy to answer any questions that folks might have about Lexical.

This wasn't the case. I left the project to focus my attention on React.

I think this may be referring to "preact-compat" issues rather than Preact issues. I know the Inferno team recently had to change a lot of the state scheduling to be 1:1 with React 15/16 (i.e. batch sync schedule setState after events was very broken and there were issues with controlled components in Safari).

A very large software company that use Inferno in production already had their legal team look into Inferno. It didn't infringe on any patents.

It would be awesome if you could give the Inferno team your feedback so we can help improve Inferno. :)

What issue did you have with Inferno, would mind reporting it please so we can fix it? :)

This isn't true anymore. Blueprints were removed from Inferno quite some time ago. Inferno uses createVNode calls, which are very much like createElement calls.

We have a Slack if you're interested: https://inferno-slack.herokuapp.com/

Inferno also has its own event system like React does.

The interview actually talks quite a bit about how I went about making these changes. Worth fully reading!

I'm sorry, this topic has nothing to do with the operating system. Inferno in this context is a popular JavaScript library for building UIs, not an operating system.

Note: I'm the author of Inferno

I commonly hear the same thing – you've benchmarked React and it performs fine. Did you benchmark this on a modern MacBook/laptop by any chance?

The realism is that the desktop market is only 15% of the entire global online market. In developing nations, Android mobile performance is essential. React, Angular, Ember and other libraries have never performed well in this space.

If you're shipping a huge bundle for your app – you're doing something wrong too. You need to take into account that mobile users are likely to have a 3G connection at best and are likely to be on a 5+ year old device. You need to endorse code-splitting, service workers and other PWA features to better accommodate those users. Inferno will deliver the best in class mobile performance when paired with those features.

Unlike Angular 1 -> Angular 2, React Fiber will be fully backwards compatible with the current React.

There's no reason why React can't learn from Inferno. In fact, I'm aware that they're using a lot of the internals of Inferno to improve React Fiber. I'm sure we'll see more on this in the future :)

Inferno is 8kb, it's smaller than the Mithril re-write and is on par with Preact in terms of parse performance. I think you may have looked at the older Inferno codebase, as the current one is very slim and readable.

Note: I'm the author of Inferno and know the authors of Preact and Ivi well.

That's a great question and one I frequently get asked. The "current" React codebase is legacy in many ways, the React team are hard at work on React Fiber which is complete re-write of the entire codebase.

The legacy codebase isn't something we can actively make better (I've had my PRs merged though) without a huge rewrite. If we tried to make changes, it would break React for many people due to how coupled many things are.

A lot has changed in the last few years and the approach to virtual DOM has been one of them. Going forward, the React team are making big efforts to change this.

This has nothing to do with React. This is a JavaScript library called Inferno – the title makes sense to people in the JavaScript scene.

Great work! Styletron looks awesome and the performance definitely fits well with some of the apps I work with. I'll give it a try :)

I never posted the Inferno website URL to Hacker News, someone else did. We should be going live with the new website in the coming week, I was hoping to post it once that had been done!

You can use ES2015 classes too and `inferno-compat` will try to support everything that React 15.4 currently supports. Recompose should work fine too, as should most common libraries. If you run into issues, please let the Inferno team know and we can investigate why. :)

If anyone has any further questions/queries/ideas/rants you can jump on the Inferno Slack - https://inferno-slack.herokuapp.com/.

The team and I would love to hear from you. We want to make Inferno better and we believe in doing so, we can start a shift in the community that starts to realise that performance on mobile with the current state of libraries and tools is not good enough. This was always the primary goal for why I began Inferno – about 2 years ago.

You totally can use Inferno. You can use a package on NPM called "inferno-compat" to alias out React to Inferno via Webpack/Babel/Browserify if you want to. Alternatively, you can use Inferno as is and it has JSX Babel plugin, all the same top-level APIs and has the same ES2015 components as React (although we've put them in their own package called "inferno-component", as some people don't use them).

I hope that helped – I'd recommend jumping on the Inferno Slack if you'd like to know/understand more: https://inferno-slack.herokuapp.com/

I completely agree and I wrote Inferno. I really do think people jump on Hacker News stories in the wrong way at times. Inferno isn't meant to make you abandon months of work because it's shiny and new – or whatever reason someone has.

I'm all for starting a conversation though. People should evaluate Inferno and see if it solves a particular problem they're having. If it doesn't and they're in a good place with what they have, then they probably shouldn't be doing it.

If anything, I hope Inferno makes other library authors realise that there is a demand for performance when it comes to PWAs on the mobile platform and, in my opinion, what we have right now in terms of options isn't necessarily great – especially on low-end mobile devices in developing regions of the world.

Will definitely do that. README writing is like an entirely different skill in itself to be honest. I'm not great at it :/

I think it looks great. We've been designing this site for a while now and there comes a point where you need to stop designing it and start building it – which is why we still don't have a site :D

note: I'm the author of Inferno.

If you're comfortable with what you have right now. I don't expect you to switch to Inferno. If you're happy with your app, it works great, it's performance is where you want it and your team/company love it – you'd be mad to switch to something because you saw it posted on Hacker News.

Inferno isn't here to make your life hard, it's giving you an opportunity to use it when the time might be right – like when you may have issues with performance on mobile (the primary reason why I created Inferno in the first place).

I also wrote Inferno so other authors of other libraries and tools could borrow the ideas in Inferno and further improve what they're trying to do. Open-source is great in that it allows us to share ideas in that way and I'd love to see other frameworks like React, Vue, Angular etc push the boundaries of performance even further.

That is so far from the truth that it's unbelievable. Inferno has the same surface API as React – the public endpoints. Everything under the hood is different though and it's different for many good reasons which I'll cover in a blog post in the coming weeks for the official 1.0 release of Inferno (and its website).

If there's nothing wrong with your app and you're using React – keep using it. If you are experiencing performance issues on mobile, maybe Inferno is an option with its compatibility layer until future versions of React can fix your issues.

Note: I'm the author of Inferno

You don't need to necessarily use Inferno in production all at all. If you're happy with React, stick with it. Inferno can serve to help other authors and the React team to further improve their tools. This is open source after all, we can all learn and improve from one another and make even better software.

That's why I claim near rather than perfect. It's a constant work in progress, that's the challenge :)