As usual the only black guy there doesn't get to talk about tech. It must either be "on diversity" or nothing showing black people do tech. I don't think it is deliberate but it perpetuates a wrong narrative. == EDIT. I was inaccurate in this case. See below
React Conf 2017 Livestream
31–40 of 49 posts
Re: React Conf 2017 Livestream
#32ReasonML doesn't seem to be on the list of presentations this conf. Will Facebook discuss this in the near future? :)
Cheng Lou works on ReasonML and is speaking tomorrow at 4:30PM PST. Talk description:
> What is a piece of code? What is a library, a tool, a platform and a language? Based on my last talk on the spectrum of abstraction, this talk explores the daily concerns and the meta-concerns of writing code, and how our new effort, Reason, relates to them.
Re: React Conf 2017 Livestream
#33As usual the only black guy there doesn't get to talk about tech. It must either be "on diversity" or nothing showing black people do tech. I don't think it is deliberate but it perpetuates a wrong narrative. == EDIT. I was inaccurate in this case. See below
http://conf.reactjs.org/speakers/ben ?
I stand corrected. Thanks ng12
When I looked through, I didn't see him. I'm happy I am wrong here.
The stats are still worrying [1]. My greatest joy will be to be continuously wrong on this
[1] http://oonwoye.com/2015/10/15/where-are-the-black-tech-found...
Re: React Conf 2017 Livestream
#34React is such BS. Its sole purpose for existing is to make simple tasks unnecessarily complicated.
After using it in couple of projects, we see it as making complex tasks really intuitive. Maybe you are using it for some wrong problem.
You're unqualified to actual have an opinion on the matter.
Re: React Conf 2017 Livestream
#35Earlier quoted context omitted.
Have you thought about using MobX instead? I think Redux's "complications" stem from guiding you towards a certain set of principles and ways of coding without giving you the tools to commit to those principles and ways of coding. Particularly, the way you compose reducers and the way you expose actions is manual and very boilerplate-ish. Mark Erikson hosts a wonderful page full of redux ecosystem links, and here you…
Mobx is far more intuitive (and fun) than Redux. It truly enables you to focus on features rather than concepts. Mobx also frees you from the "Redux architecture", which I found to be difficult and contrived...
Mobx? Seriously? Another unqualified one to have a opinion on the matter.
Re: React Conf 2017 Livestream
#36Earlier quoted context omitted.
http://conf.reactjs.org/speakers/ben ?
I stand corrected. Thanks ng12 When I looked through, I didn't see him. I'm happy I am wrong here. The stats are still worrying [1]. My greatest joy will be to be continuously wrong on this [1] http://oonwoye.com/2015/10/15/where-are-the-black-tech-found...
As someone who was involved in speaker selection, I agree. We'll keep pushing on this and hopefully do better next year.
Re: React Conf 2017 Livestream
#37Earlier quoted context omitted.
I had the same feeling. Coming from ExtJS and Ember, React felt rather simple. But Redux is a whole nother story :(
Have you thought about using MobX instead? I think Redux's "complications" stem from guiding you towards a certain set of principles and ways of coding without giving you the tools to commit to those principles and ways of coding. Particularly, the way you compose reducers and the way you expose actions is manual and very boilerplate-ish. Mark Erikson hosts a wonderful page full of redux ecosystem links, and here you…
I'm currently in the process of migrating a decently large React app from poorly written React/Flux to (hopefully) better written React/Redux, and I'm definitely feeling the lack of...useful examples. A ToDo list or showing lists of users from Github just doesn't cover the realistic complex problems well. Thus, when I encounter one of those problems, and Google fails me, I have to take a stab at it...and likely recreate the not-best-architectures of those that have done the same before me.
I'm still happy with Redux so far - the patterns it encourages is at least an improvement over the code from before, but I can't shake the the feeling that there are basic mistakes I'm making because I only have a handful of best practices goals.
Re: React Conf 2017 Livestream
#38For anyone interested in more details about React Fiber, the recommended links in [0] provide a great jumping-off point. For many apps, especially ones that render large amounts of data to a screen and haven't done (or can't do) much optimizing with componentShouldUpdate, it will likely be an almost-seamless drop-in upgrade that will make things feel truly more "snappy." A video (of a demanding stress test) is worth…
I wonder how React fiber will stack up against preact. Both in performance in areas like animation and in more "regular" workloads.
The creator of Inferno joined the React team a while back. Performace wise, I'm sure some of that Inferno magic will be there
Re: React Conf 2017 Livestream
#39Earlier quoted context omitted.
I had the same feeling. Coming from ExtJS and Ember, React felt rather simple. But Redux is a whole nother story :(
Have you thought about using MobX instead? I think Redux's "complications" stem from guiding you towards a certain set of principles and ways of coding without giving you the tools to commit to those principles and ways of coding. Particularly, the way you compose reducers and the way you expose actions is manual and very boilerplate-ish. Mark Erikson hosts a wonderful page full of redux ecosystem links, and here you…
In theory I like the basic ideas around redux, reducer composition is a very cool idea. However I really hate the implementation, the amount of boiler plate code is just too high.
Re: React Conf 2017 Livestream
#40ReasonML doesn't seem to be on the list of presentations this conf. Will Facebook discuss this in the near future? :)
Cheng Lou works on ReasonML and is speaking tomorrow at 4:30PM PST. Talk description: > What is a piece of code? What is a library, a tool, a platform and a language? Based on my last talk on the spectrum of abstraction, this talk explores the daily concerns and the meta-concerns of writing code, and how our new effort, Reason, relates to them.
I overlooked this talk. My apologies.