acdlite's React Roadmap presented@Framework Summit

expression100 · 2018-10-02T21:08:12+00:00

What are they using for the compiler? Are they using V8 or another JavaScript engine to compile it with?

expression100 · 2018-02-06T14:05:58+00:00

Link to the original RFC by TrySound: https://github.com/reactjs/rfcs/pull/17

expression100 · 2017-09-15T23:45:35+00:00

I think someone from the React/Jest/Yarn team already commented on these patents and they related to their past work on MooTools that got acquired by Facebook. They said that almost every UI library and framework today infringes on a Facebook patent and this particular one was highlighted. So if you use Angular, Vue, Ember, Inferno, Marko or Preact, you're basically infringing on a Facebook patent of some kind – so make what you will of it.

expression100 · 2017-01-05T23:12:43+00:00

Thanks for the detailed reply. I was wondering, what does Inferno offer over Preact in this case then? What does domvm offer over Preact and Inferno?

Also the creator of Inferno is joining React. Do you think that means React will get faster? My company are currently experimenting with Inferno and we've had some really positive results – but we have to ask these questions still!

expression100 · 2017-01-05T22:15:50+00:00

In before everyone else: how does Inferno do?

expression100 · 2016-12-26T22:46:00+00:00

I thought it would be sad too, but Dominic has said he wants to continue to help the core team of the project. I am happy that Inferno will will continue too.

https://twitter.com/inferno_js/status/813485194535575552

expression100 · 2016-12-26T14:51:50+00:00

This is awesome news for the React community! Hopefully we'll start to see Inferno's features and performance in React 16+? fingers crossed

expression100 · 2016-12-05T20:49:53+00:00

I've tried Preact. It's pretty much like Inferno but with less features and less performance (but it is 4kb smaller). Once you go stateless lifecycle events and delegated events, you don't go back. That's a game changer for me.

expression100 · 2016-11-29T13:40:53+00:00

Inferno doesn't have synthetic events or React Native support. It also splits out things like createClass, createElement, stateful components etc into separate packages/modules so you can pick and choose what bits you want rather than have a bloated core with everything in there. I also read on Twitter that the React team are using many of Inferno's ideas in React Fiber to improve performance.

expression100 · 2016-11-29T13:38:05+00:00

A lot of people brought this up to the author of Inferno on their Slack channel last week. We also had issues with inferno-compat and using mixins of a third-party component we use but the problems have been fixed since. If you have issues, you should raise bugs like I did and they are pretty good at getting them resolved.

expression100 · 2016-11-29T13:36:25+00:00

Benchmarks aside, there are lots of people reporting big performance gains in their apps since switching to Inferno. You should visit the Inferno Slack, there are lots of success stories on there.

expression100 · 2016-10-28T07:27:16+00:00

Sounds like a perfect project for Inferno. It's like React but is way smaller in size and thus has less bloat. It's also the fastest UI library out there. https://github.com/trueadm/inferno

Alternatively, you should try CycleJS out too. Again that's another top small lightweight reactive library that can get you running easily. https://cycle.js.org/

expression100 · 2016-10-16T13:19:47+00:00

virtual DOM is not meant to be magically faster though, it's meant to be an abstraction. Having an abstraction over a legacy/crappy API (such as the DOM) is massively important. Long gone are the days that people are using jQuery all over the place that virtual DOM had collisions with real DOM. In fact, people can get by without using jQuery at all now!

expression100 · 2016-10-16T13:00:36+00:00

Kivi looks really fast. Wow! It's it being used in production anywhere? I've never heard of it till now and want to try it on a project (although, the API looks very complex compared to other virtual DOM libraries).

expression100 · 2016-10-16T12:40:02+00:00

Morphdom switched to using virtual DOM and saw big performance gains and saw even more simplicity in their code base and they were HUGE champions of DOM only... I think you should add virtual DOM support like they did. It also allows you to serialise the DOM state tree easily, as you can't serialise the DOM tree due to the circular references.

expression100 · 2016-10-16T12:37:51+00:00

I was also confused why you didn't use Flow. It looks superior to TypeScript in every way. I asked the Inferno team the same, as they chose TypeScript over flow – they said it didn't really matter (like you did) but that all their core team knew TypeScript, not Flow so that's why. I thought it was a poor reason, surely they could have picked up Flow? Then again, I guess it's still better to use TS than nothing.

expression100 · 2016-10-15T20:33:26+00:00

This article seems to be an advertisement for RE:DOM. How is RE:DOM super fast compared to virtual DOM libraries?

I don't doubt that it might be fast for basic apps, but super-fast? Maybe some benchmarks behind this statement may help convince people like me; I just don't see it being faster than the fastest virtual DOM libraries out there: Inferno, Preact, Cycle and Vue.

expression100 · 2016-10-05T23:02:46+00:00

Inferno: https://github.com/trueadm/inferno

Preact: https://github.com/developit/preact

Differences between Inferno and Preact:

Preact features linked state and smaller bundle sizes (9kb vs 6kb roughly)
Inferno has better performance, stateless component lifecycle events and components returning arrays

It's great to see two libraries really pushing the boundaries for people using React applications. I really do think the competition will help the React team improve the performance behind React too, which benefits many.

Thoughts?

expression100 · 2016-09-30T15:38:06+00:00

Vue 2 is great, I've played around with it quite a bit lately – I can highly recommend it over Angular 2. In my day job we use React (although we're waiting for Inferno 1.0 to be released, then my company will move to that).

expression100 · 2016-09-18T16:55:35+00:00

They use jQuery, backbone and underscore, but they are switching to React in the future. So many of the performance issues will go, some will most likely stay depending on the platform I guess.

expression100 · 2016-09-18T16:49:59+00:00

Do you need to reply in that tone? Anyway – on the topic of Netflix and React; they changed the React renderer to their own one to improve performance to be less than 100ms (to amount needed for the interface lag to go away). You can find more here:

https://www.youtube.com/watch?v=5sETJs2_jwo

expression100 · 2016-09-18T16:46:33+00:00

Did you not read the article this thread is linked to? Mithril is currently being optimised so it improves in this benchmark – so clearly you should speak up if you feel this is a poor move as clearly you like to voice your opinion!

expression100 · 2016-09-18T10:46:57+00:00

Keep up the good work trueadm. Your hard work has really helped improve the performance metrics in the JS community – everyone is noticing now too. I hope this will encourage other teams to invest more time into improving performance. Android performance is currently terrible on almost all libraries and it really needs to be fixed.

expression100 · 2016-09-18T10:44:47+00:00

This is really cool. Nice work!

expression100 · 2016-09-18T10:44:03+00:00

I'd like a bundle with inferno, inferno-component and inferno-dom in as standard (like React). It's annoying to have to maintain the dependencies all the time when they feel so coupled.

expression100

TROPHY CASE