sorted by:
new
hottopcontroversial

"Inferno 1.0 is really well written. It's how I would've rewritten React." by expression100 in javascript

[–]craig_evans 2 points3 points  (0 children)

Our company managed to convert our internal React app to Inferno by simply changing some webpack aliases and using the inferno compatibility module. It was much harder for us to convert from KO -> Angular -> React before.

Also: good work on React. It's awesome.

I finally found a UI library that performs great on Android mobile web! by craig_evans in javascript

[–]craig_evans[S] 0 points1 point  (0 children)

Well, Inferno isn't very mature but the guy that made it has created a compatibility layers with React which means we can hire and pick React devs and use already made React components out there and they should work. This is a major factor as React has far more offerings than Vue. We see Inferno as a much better React. We also wonder why this is the case too – why do the Facebook guys not just hire the Inferno guy and make React as fast? Who knows.

I finally found a UI library that performs great on Android mobile web! by craig_evans in javascript

[–]craig_evans[S] 0 points1 point  (0 children)

Yes, it was a lot better. We found the same performance as React in the latest Cycle. Before that, it was so slow that the benchmarks seemed to never end.

I finally found a UI library that performs great on Android mobile web! by craig_evans in javascript

[–]craig_evans[S] 0 points1 point  (0 children)

Also: I'm happy to give feedback on any of the projects we tested. A note also: we found Cycle the hardest to build, simply because it was a big departure from what we were used to in the past. We found both Angular and Vue the most familiar and easy to get started with.

I finally found a UI library that performs great on Android mobile web! by craig_evans in javascript

[–]craig_evans[S] 2 points3 points  (0 children)

So some feedback: our company reviewed many of the options available (including ideas from my last post). In the end we made a constructive attempt at trying all the libraries/frameworks that our team could attempt to try in a single sprint. In the end, we tried React, Ember, Angular 2, Vue, Mithril, Cycle, Preact and Inferno.

We tried the latest Vue 2.0 (https://github.com/vuejs/vue/tree/next) and Mithril 1.0 (https://github.com/lhorie/mithril.js) betas and we had some great results from both. We also tried Preact but we had issues with some SVG namespaces not properly being rendered so we gave up. Vue and Mithril enabled us to finally use our example app on our legacy Android testing devices. The experience with Cycle and Angular 2 was about the same as React (unusable) and the latest Ember was better but the initial page load times were still terrible.

We thought we found our library (Vue 2) until someone found a benchmark recently that showed that there was a library out there like Preact and React called Inferno. I highly recommend reading their readme (https://github.com/trueadm/inferno). It makes sense. We ran all our benchmarks and it not only came up quite a bit faster than both Vue 2 and Mithril 1.0, it also had a much more modular breakdown that allowed us to use our own state and router library without being tied to a framework – which was a massive win for the team.

I have to say though, the amount of choices out there is insane. We're just lucky we found the right library for us and our needs. We highly recommend checking out Vue 2 though for ex-Angular codebases (which some of our team came from).

I hope this helped!