acdlite

5 ms·

1.
by acdlite 4y ago
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 solution I'd recommend for React tests going fo
2.
by acdlite 5y ago
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, feel free to tag me or someone else on the
3.
by acdlite 5y ago
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 framework. Like, yes, implementing batching in React was
4.
by acdlite 5y ago
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 imports), we'll likely wait until the next major rele
5.
by acdlite 5y ago
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 event will always be processed sequentially. We d
6.
by acdlite 9y ago
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 empty tags is meant to represent
7.
by acdlite 9y ago
> The Fragment syntax adds some additional magic to JSX (which is rarely a good thing) In: <></> Out: <React.Fragment></React.Fragment> WITCHCRAFT!! SORCERY!! Teasing aside, I don't get what's
8.
by acdlite 9y ago
Fixed now! Thanks for the bug report!
9.
by acdlite 9y ago
Submit a PR :)
10.
by acdlite 10y ago
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 a component's children in the form of props. Centralize
11.
by acdlite 10y ago
I believe the ultimate goal is web apps with 60 fps gestures and animations.
12.
by acdlite 10y ago
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 priority. Or a DOM element with display: none will automatical
13.
by acdlite 10y ago
When you call setState on a component, only that component's subtree is reconciled and re-rendered.
14.
by acdlite 11y ago
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, you will engage in solving technical problems from t
15.
by acdlite 11y ago
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 useful for stateless functional components :)
16.
by acdlite 11y ago
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 direction. One example: https://github.co
17.
by acdlite 11y ago
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 reasoning here: https://www.youtube.com/watch?
18.
by acdlite 11y ago
> 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 opinion. I'm curious what the author's obj
19.
by acdlite 12y ago
- 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 "classes". It's not like you're lo
20.
by acdlite 12y ago
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, "smart" components do things l
21.
by acdlite 12y ago
Or instead of a Make-like tool you could just use Make itself :) Works really well.
22.
by acdlite 12y ago
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) working and everything, and you can always write a Bash&#x
23.
Eyeglass – NPM Modules for Sass(github.com)
3 points by acdlite 12y ago|0 comments
24.
by acdlite 12y ago
That's actually the default, but you can specify a different module system if you like. https://babeljs.io/docs/usage/modules/
25.
Show HN: Flummox – Isomorphic Flux library with zero singletons(github.com)
3 points by acdlite 12y ago|0 comments
26.
Why components are better than mixins in React(github.com)
1 points by acdlite 12y ago|0 comments
27.
by acdlite 12y ago
Nailed it.
28.
by acdlite 12y ago
Bad abstractions are dangerous. Good abstractions are empowering. cough React Native cough
29.
by acdlite 12y ago
Ah, I see. I don't really agree, because I think the enforced unidirectional data flow is one of the best parts of React, but that's certainly a valid point of view. I just want to emphasize again that Flux is entirely possible wi
30.
by acdlite 12y ago
Agree that singletons for Flux are bad, but they're totally not necessary (e.g. https://github.com/acdlite/flummox ). And if you don't like Flux, don't use it. I don't see how that's can be a de

More ›