lots of users are going to encounter the same challenge but not be #winning like #MotherFuckingDanAbramov. 4/4
-
-
I don’t think dividing functions into functions is very clever, but yes, it is required for using Redux successfully.
2 replies 2 retweets 36 likes -
Replying to @dan_abramov @tomdale
your argument was, more or less, that Tom should have remembered about .filter(). It's probably not that Tom 1/
3 replies 0 retweets 4 likes -
wasn't *aware* of .filter(), but that he didn't think of it here. The fact that you remembered it isn't an answer. 2/2
6 replies 0 retweets 3 likes -
The original post felt contrived due to saying that framework implied boilerplate code 1/
1 reply 0 retweets 1 like -
That strategy could be applied to any framework, eg Ember or Redux. 2/
1 reply 0 retweets 2 likes -
Thus responding with a different syntax seems valid. Perhaps the Redux docs could encourage that style? 3/3
4 replies 0 retweets 2 likes -
you can: A) cheerfully learn B) keep doing it your way, why all the whining?
1 reply 0 retweets 0 likes -
Replying to @papakoleok @pspeter3 and
I don't think that's how the Ember community has operated in practice. 1/
1 reply 0 retweets 0 likes -
Replying to @wycats @papakoleok and
as far back as 2014 we actively changed Ember from React learnings 2/ https://github.com/emberjs/rfcs/blob/745cf72ac8e1a00d1748274e308d3b990979facc/active/0000-the-road-to-ember-2-0.md#learning-from-the-community …
1 reply 0 retweets 0 likes
a big chunk of the linked 2.0 RFC was about adopting React data-flow. 3/3
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.