Viewing profile — acdlite

Not sure what Enzyme's plans are, since I know they depend on some React internals. However, we've worked closely with the React Testing Library maintainers, and that's the solutio…

Who are these jerk users? I'm going to give them a noogie! In all seriousness, I'm sorry you had such a bad experience. That's not what we want the React community to be. Next time…

I agree the React implementation is very complex, but in a way that's by design: we add features to React when it allows us to move complexity out of our product code and into a fr…

We do intend to ship a ES module build of React in the near future. Because that's a breaking change that could require significant changes to existing apps (i.e. to update the imp…

We have a mechanism to handle this exact scenario. We classify certain user input events, like keypresses and clicks, as "discrete" events. Updates that are triggered from discrete…

We did mention some prior art in the section discussing the new syntax: > Fragment syntax in JSX was inspired by prior art such as the XMLList() constructor in E4X. Using a pair of…

> The Fragment syntax adds some additional magic to JSX (which is rarely a good thing) In: Out: WITCHCRAFT!! SORCERY!! Teasing aside, I don't get what's magical about this. It's a …

Fixed now! Thanks for the bug report!

Submit a PR :)

setState is a public API, usually triggered in response to a user event like a click or an input change event. State in React is local to a component, but it can be passed down to …

I believe the ultimate goal is web apps with 60 fps gestures and animations.

I believe the idea is to expose as little of the prioritization details as possible. E.g. updates triggered by a text input's change event will automatically receive higher priorit…

When you call setState on a component, only that component's subtree is reconciled and re-rendered.

OpenGov | Redwood City, CA | ONSITE Full-Stack Engineer We're innovating, solving big challenges and having fun while doing it. As a senior member of OpenGov's engineering team, yo…

Thanks for the link! Should clarify that Recompose works equally well with stateful components created with either createClass or React.Component. It just happens to be especially …

The presentation has some really great points; it's a shame that it's wrapped up in so much FUD. But from what I can tell, it does seem like React is moving in a more reactive dire…

I disagree, but I suppose this a matter of preference. For whatever it's worth, the React team did explore using a constraint-solver, but nixed the idea. They explain their reasoni…

> Flexbox. The authors missed the opportunity of offering a saner API and favored sticking to the official spec instead. Flexbox is the saner API we've all be waiting for, in my op…

- More declarative. - Harder to screw up. Even if you know what you're doing, prototypical inheritance involves several steps which can get repetitive. - Interoperable with non-es6…

Like spicyj said, the wrapper components pattern works really well. Some people have started referring to this as a separation between "smart" and "dumb" components. For instance, …

Or instead of a Make-like tool you could just use Make itself :) Works really well.

I went from grunt to gulp because of streams, then I went from gulp to make because of Unix. Takes some getting used to, but I'm very happy with it. Got livereload (hot reload) wor…

That's actually the default, but you can specify a different module system if you like. https://babeljs.io/docs/usage/modules/