React.js Conf 2016 - Ben Alpert - What Lies Ahead
Meta Developers0 HN recommenders · 2016–2016
50K views · talk · dated · Uploaded 2016-02-24
Ben Alpert of the React team talks at React.js Conf 2016 about where React is heading. He covers performance and stability work, challenges at Facebook, and opportunities such as bringing React Native ideas to the web.
HN points to it as a primary source for what the React team was actually working on, such as React Native for the web.
38:47RailsConf 2014 - All the Little Things by Sandi Metz
Confreaks
1:01:39"Simple Made Easy" - Rich Hickey (2011)
Strange Loop Conference
26:53What the heck is the event loop anyway? | Philip Roberts | JSConf EU
JSConf
36:45Rich Harris - Rethinking reactivity
You Gotta Love Frontend
25:06"Making Impossible States Impossible" by Richard Feldman
elm-conf
1:00:19How To Design A Good API and Why it Matters
Google TechTalks
31:44The Value of Values with Rich Hickey
InfoQ
1:04:04Overwatch Gameplay Architecture and Netcode
GDC Festival of Gaming
3 comments from Hacker News
I tried submitting a reddit thread ( [LINK] ), but it didn't get much traction... I think because the videos got pulled. I hope you guys don't mind if I ask this question here, and I apologize if I'm being naive in some way: Aditya Punjani's later Flipkart talk ( [LINK] ) mentioned the importance of mobile web apps and 60 FPS. Ben Alpert's talk mentioned ( [VIDEO] ) "React Native for the web" would be awesome. There was even a lightning talk on react-native-web which attempts to do this using the traditional DOM ( [LINK] ) Whatever happened to Flipboard's React Canvas ( [LINK] and [LINK] ) being a solution to these problems? There's pretty good browser availability and although there's currently no perfect solutions for things like accessibility, SEO, or server-side rendering... I failed to se a real "nail in the coffin". Did it just never gather enough momentum?
There's a touch more than views to consider, e.g. do you have to build or want a native mobile app? Angular 2.0 will be under heavy development whereas I think React has matured to the point where a lot of effort is going into ease of use and performance [1]. I also found the React tool chain (using webpack/babel5) very slightly more sane than grunt/gulp once my project grew beyond "Hello TODO". But the JS tooling is absolutely crazy no matter what platform is decided. I'm using redux for API calls - I like the "single store" approach despite drawbacks vs. flux (or multiple stores). [1] [VIDEO]
They are specifically working on it according to this React.js Conf talk [0]. There's also rwb from Pete Hunt [1]. EDIT: Removed comment about 'standard'. Ain't so bad anymore apparently. [0] [VIDEO] [1] [LINK]