I suspect you cannot be nearly as critical of the build as I am
them implement things that Ember CLI solves. Ember CLI is not a technical solution 4/
-
-
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.
- 6 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.