> This is exactly the type of thing using React for the view layer would address. I always found myself making extra components and 4-6 files then contriving ways to communicate between them. I'm quite sure there's a reasonable way to handle this in Ember, but when I do similar things in React, I don't have to look anything up. I just write javascript and things behave the way I think they should.
Ember is really not-friendly if you fight the 'ember way of doing things' (e.g. shared-state computes down, events bubble-up). There are a few edge-cases I've had where a parent really needed access to it's child and I am personally not a huge fan that Ember is so opinionated about not doing it, but I would say this is akin to the GoLang's kind of opinionated, it might hurt a few times but it generally standardizes the code-base which is very important when multiple people might be touching related code.
Ember is really not-friendly if you fight the 'ember way of doing things' (e.g. shared-state computes down, events bubble-up). There are a few edge-cases I've had where a parent really needed access to it's child and I am personally not a huge fan that Ember is so opinionated about not doing it, but I would say this is akin to the GoLang's kind of opinionated, it might hurt a few times but it generally standardizes the code-base which is very important when multiple people might be touching related code.