[clintjhill]

  Your day job is to build a piece of web software and you can’t take a few days to learn the ins and outs? 

This is the opinion I had when all of the previous Ember flare ups happened. My thoughts were exactly this. It would behoove so many of us to simply spend more time with new technology and ideas before we simply throw our hands up and say "it confuses me".

[delinka]

"Confusion" is not the word I would use.

Metaphorical "you" alert, not directed at parent:

You have a new-fangled thing for everyone to use. Scratch that, everyone who's been in your shoes, with your particular pains. Great, you solved a problem. Take some time to explain on your blog or in your GitHub README.md the context of your solution. "Because I can!" is a fine reason, but I don't spend time exploring something that was built because it was possible to build it.

So your new-fangled thing looks like it's a solution to a problem I'm having. I start to implement it and ... oh dear $DEITY, it's a mess. I don't mean it's ugly, I mean it's completely inextensible. It's a specific solution where a generic one would suffice. Or worse, you didn't think outside your little box to discover that this "fix" will debilitate 95% of the web servers on the planet if they were to try this solution.

My advice: if you build it, A) explain why, B) learn to build it well.

[clintjhill]

Fair. I'm only suggesting that before we collectively steam roll an open source project and its volunteers with "I don't get it, so it sucks" mobs, that maybe we spend a weekend with it. Maybe over that weekend we learn "oh dear $DEITY". And maybe, just maybe we contribute back to it in an effort to "help".