Re:Technologies in HN “Who is Hiring?” threads
by forgotpwtomain on Tuesday August 23, 2016 @03:24PM
(#12346690)
> 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.
For context, the app was well over 10k loc, and was a socket connected video chat (+ contacts) application. I had enough experience with Ember to upgrade the app from 1.3 to 2.x stopping regularly along the way. I do expect knowing Ember more thoroughly would have helped but that was always my problem: I felt like I had to be intimate with every aspect of the docs to get the simplest things done. Towards then end I was spending a great deal of time which felt antithetical to the entire point of using Ember.
> Really? I think the React model of inlining HTML in your Javascript is atrocious
I suspect there will always be a segment that would prefer not to use JSX / inline templating, and that's totally ok.
> Ember is sometimes painful in ways that jQuery wouldn't be (e.g. what I don't have access to the children components of my component!)
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.