them implement things that Ember CLI solves. Ember CLI is not a technical solution 4/
-
-
Replying to @wycats @richardiii and
it establishes a shared community workflow that encompasses plugins/addons 5/
2 replies 0 retweets 0 likes -
Replying to @wycats @richardiii and
maybe you don't think the conflict between react-router and redux was a "real issue" 6/
1 reply 0 retweets 0 likes -
Replying to @wycats @richardiii and
but it's one of many, many issues people have had to solve on an ad-hoc basis. 7/7
1 reply 0 retweets 0 likes -
Replying to @wycats @stefanpenner and
I have been able to move from many react projects to another and usually understand it well
1 reply 0 retweets 0 likes -
Replying to @richardiii @wycats and
this was not the case for ember. Sure directories and routing. OK. But business logic, no.
2 replies 0 retweets 0 likes -
Replying to @richardiii @stefanpenner and
this is the opposite of what companies that have adopted both React and Ember have said.
1 reply 0 retweets 0 likes -
Replying to @wycats @stefanpenner and
I know the problem you are trying to fix there. I am saying it has not been my experience though
1 reply 0 retweets 0 likes -
Replying to @richardiii @stefanpenner and
I think it's easy to conflate problems with a solution w/ a category of solutions.
1 reply 0 retweets 0 likes -
Replying to @wycats @richardiii and
many big Ember apps exist and haven't collapsed into incomprehensible complexity.
1 reply 0 retweets 0 likes
but most big Ember apps have people fluent in the lower-layer public API.
-
-
Replying to @wycats @richardiii and
it's bad that we haven't made this a much more direct part of the experience of Ember.
1 reply 0 retweets 1 like - 3 more replies
New conversation -
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.