wingspan

8 ms·

31.
by wingspan 10y ago
Fantastic, thank you for making me laugh so much. Almost makes up for the years spent being tortured by CSS just so I could appreciate your tale.
32.
NES Classic Edition(nintendo.com)
2 points by wingspan 10y ago|0 comments
33.
Discontinuing IE 8 Support in React DOM(facebook.github.io)
3 points by wingspan 11y ago|0 comments
34.
Mutations in Relay [pdf](speakerd.s3.amazonaws.com)
1 points by wingspan 11y ago|0 comments
35.
by wingspan 12y ago
Absolutely! It is really hard to write idiomatic code your first time through with a framework. No need to feel silly at all. No way I would have spotted these things if I hadn't been using React every day for the past year or so!
36.
by wingspan 12y ago
Because if you are doing React and JSX you are already using JSTransform. If it gets you most of what you need, why add another dependency?
37.
by wingspan 12y ago
Not a bad idea. We would typically use _onClick for any component handler methods, so the _ would distinguish it. We have an internal transform that mangles anything in a module starting with _ so that it cannot be accessed outside.
38.
by wingspan 12y ago
Thanks for putting this together, always interesting to see people use React for the first time! I did a code review of sorts and cleaned up the code to be more idiomatic React. You can find the series of commits with in-depth comments on G
39.
by wingspan 12y ago
In case anyone is looking for this: https://nicolasamiot.wordpress.com/2013/07/25/inkscape-nativ...
40.
by wingspan 12y ago
Missing from this great guide was any mention of moss, an issue I never thought about until moving to the Pacific Northwest. Now my lawn is mostly moss with some grass sticking through. I have resigned to just let it grow, since it is soft
41.
by wingspan 12y ago
Missing from this great guide was any mention of moss, an issue I never thought about until moving to the Pacific Northwest. Now my lawn is mostly moss with some grass sticking through. I have resigned to just let it grow, since it is soft
42.
by wingspan 12y ago
I meant to mention this; the helper mixin I was referring to is called StateFromStore, and it fetches data from stores and shoves it into state via setState.
43.
by wingspan 12y ago
I didn't develop React, I just use it at Facebook. I started Javascript development at Microsoft where we were using mostly our own homegrown stack on www.so.cl. When I moved to Facebook, the entire project I'm working on is in Re
44.
by wingspan 12y ago
Sure, that is absolutely a valid scenario. This could be accomplished using a context object as I explained in my first comment, something like {changedFields: ['isFavorite'], error: 'some error message'}. You'd the
45.
by wingspan 12y ago
Ah of course, I was reading it wrong. Thanks.
46.
by wingspan 12y ago
That's about right. We really only use state for transient display properties, mostly toggling display of some component.
47.
by wingspan 12y ago
Ah right, I thought so. So as long as @hcarvalhoalves is using a recent version they should be fine.
48.
by wingspan 12y ago
I believe the latest version of React does autobinding on component methods, so you shouldn't need .bind(this). There should be a warning letting you know this (unless it is different for the public version :/).
49.
by wingspan 12y ago
We split out data mutations from data access (see https://news.ycombinator.com/item?id=7721542 ). One reason is that multiple stores may be interested in the COMPLETE calls. One example is when you have a store that tracks w
50.
by wingspan 12y ago
No! Never access the DOM directly if you can help it. I forgot to mention, display things like you said are one of the only places we really use local state. A dropdown for instance, might have a state called "isOpen". In your cli
51.
by wingspan 12y ago
Don't cursors still suffer from the problem of intermediate components needing to pass on state they don't use? For example, a list of articles might have an author for each article. Then you have the following components: App &gt
52.
by wingspan 12y ago
Yes, it is the dispatcher. ArticleActions.update basically calls Dispatcher.dispatchAction(ARTICLE_UPDATE, {article: article})
53.
by wingspan 12y ago
Good question. I haven't used backbone at all, and only know what I've read about it. Flux is a complete replacement for backbone as far as I can tell. As you say, the models live in stores, so building on my other comment, you wo
54.
by wingspan 12y ago
We had talked about using promises at a lower level, but for actions it is very desired for them to be fire and forget. The view (component) fires the action in response to some user interaction (e.g. clicking a button). The action is dispa
55.
by wingspan 12y ago
From first-hand experience, I can say that React+Flux has scaled well to 8+ developers over 800+ JS files and ~60k lines of code in a large single page app here at Facebook. I'm happy to answer any questions! Some things that we'v
56.
by wingspan 13y ago
Last time we used Airbnb was for an apartment in Copenhagen. We found out when we arrived that instead of the "Whole apartment" as it was listed, we would be in one room and sharing the rest of the place with the owner and her dau
57.
by wingspan 13y ago
Interesting! I worked in that same office when FUSE Labs was there in the post-Ozzie time (2012), and like some of the other commenters pointed out, I never saw a single one of my coworkers doing actual work outside of their offices. It was
58.
by wingspan 13y ago
I was hoping (by the title) that this was something about generating real-looking test data for your app, something very useful for UI devs before the API or backend is in place.
59.
Motorola Skip(motorola.com)
1 points by wingspan 13y ago|0 comments
60.
by wingspan 13y ago
No reason in particular, just put it together quickly. Yours is a good option since it keeps the DOM count low instead of letting it grow as you mouse around :)

More ›