for I know where more of the bodies are buried
it establishes a shared community workflow that encompasses plugins/addons 5/
-
-
maybe you don't think the conflict between react-router and redux was a "real issue" 6/
-
but it's one of many, many issues people have had to solve on an ad-hoc basis. 7/7
-
I have been able to move from many react projects to another and usually understand it well
-
this was not the case for ember. Sure directories and routing. OK. But business logic, no.
-
this is the opposite of what companies that have adopted both React and Ember have said.
-
I know the problem you are trying to fix there. I am saying it has not been my experience though
-
I think it's easy to conflate problems with a solution w/ a category of solutions.
-
many big Ember apps exist and haven't collapsed into incomprehensible complexity.
- 5 more replies
New conversation -
-
-
npm install is better than any add-on system imo
-
I know cli hits the 90% case. Sometimes you need some extra engineering, and then it's painful
-
I think the problem is that the low-level primitive is poorly documented and not always 1/
-
well exposed (but usually just poorly documented). 2/2
End of conversation
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.