181 karma · joined January 7, 2009
If you want, we could put this up on the React Native Blog. Would make for an interesting read !!
Also, here is a list of all the things that our team has been working on with React Native - https://www.youtube.com/watch?v=1hvQ8p8q0a0
> On the documentation The document is not abandoned. Infact, we are actively working on fixing the document and reaching out to the community to identify gaps in documentation and fixing them. We are also moving docs to a separate repo to make sure that they are easy to contribute to.
> On Typed languages. A lot of people use React Native with Flow or TypeScript, and are able to benefit from type systems.
I would also recommend not using CodePush to completely what an app does.
CodePush will also be integrated into Mobile Center, so that you can also making CodePush a part of your CI process. We are also working on adding support for Authentication, storage, testing and Push notifications.
[I am the PM on CodePush and React Native Mobile Center stuff]
Would love to hear any other feedback you may have on the authoring experience.
(1) cancelling events which are synchronous, but web worker communication is async
(2) What is the best serialization format ? I found JSON.stringify to be the fastest, but how to compress data better ?
(3) How to batch the operations when you want to send info over from worker to the UI thread. The batch size should be small enough that it runs in 16ms, but large enough that you don't waste frame cycles.
(4) Figuring out if it makes sense to spawn multiple workers to diff parts of the VDOM tree - similar to React Fiber
Some of the other uses typically are - sort of flow control between the thread and the worker, so that only sufficient VDOM operations are sent across the thread.
This basically leaves the UI thread to other things like GIF animations, redraw UI like buttons when user interacts with them, etc.
I just run the packager, with watchman and flow disabled, and it works pretty well. The VS Android emulator is free and so much faster than the default emulator - thats why i use Windows to create Android apps atleast.
You are right - this was announced at ReactConf 2016
Have seen some interesting trends with these frameworks, like how Ember's new rendering engine is 25% faster, etc.
Getting a huge score, but the server is overloaded, so cannot post high scores :P
I was hoping that just like Todomvc.com shows how to use a framework, this could be used to see the performance of web frameworks.
Some quantitative results - http://blog.nparashuram.com/2015/03/performance-comparison-o...
http://blog.nparashuram.com/2015/03/performance-comparison-o...
Here is a run for canIuse using the automated tool - http://www.perfmonkey.com/#/trynow/results/travis/53663113
Here is the result I got - http://www.perfmonkey.com/#/trynow/results/travis/53664194
Here is a test I ran on bootstrap CSS library over all its versions - http://axemclion.github.io/bootstrap-perf
- http://github.com/axemclion/browser-perf. To quickly test your website, check out http://www.perfmonkey.com/#/trynow
You can use the metrics from this tool to find out which CSS or JS make a webage janky, which action caused multiple paints, etc.
Completely written in Node, can run as a node module and a CLI.
You can get graphs like this - http://nparashuram.com/perfslides/perfjankie.
- Based on Chromium's perf framework, needed a way to monitor performance everytime I deploy a site, automatically.