"This reaction to Ember just baffles me. 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? Presumably yo

"This reaction to Ember just baffles me. 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? Presumably you’re in a large team because this project is important and will take some time to complete. " What the hell is this!? Your day job is to write software, perhaps, but you're going to come across Ember/X new web framework/whatever in your free time first. You're going to try it because you've seen the name floating around and it sounded cool. And - discover that it's impenetrable. That it acts like it wasn't designed for people to learn. That it starts frustrating and stays that way, when you were looking for a fun new project that moves fast and get results. Why would you keep going? Why would you give it time and then force your teammates to do the same thing, when the developer couldn't be bothered to make their software accessible? Why is it worth your time, as a human, to waste effort because someone who wants you to use their software couldn't be troubled to really try? I don't understand what people are thinking when they create a brilliant, complex piece of software, and don't dedicate concerted effort to making it the easiest thing to learn ever. So - you want people to use your product, but only if the have to suffer? Or - you and your team have talked and decided you want some users, but, you know, definitely not too many, so you make it take a high activation energy to get started. Software lives and dies by its barrier to entry and documentation. And far too many projects have far too little of both these days. *I understand Ember is improving, especially after that post. Good! I haven't actually used it; I'm just going off what I read the other day.