Good question. The Ember reference isn't a religious statement in the holy war of frameworks.

It's about targeting contribution and letting potential contributors know what we're using so that they can know and self-select.

Goal #1 of the site currently is recruiting contributors b/c we aren't at a 1.0 release yet. We have it running in several hospitals in the charitable network that I serve, but it's not ready for wider distribution yet.

We want to get there by July 2016. Once we get there, we'll refocus the purpose of the homepage.

Not listing and/or not emphasizing the core component of your product can lead to confusion and (possibly intentional) misrepresentation.

I've seen situations in real life where someone will say "hey this tool is cool, how did they make it?" and another person "oh they used framework X, I think." A good chunk of people will then do their due diligence and discover that it was Framework Y not Framework X... but not everyone.

There are some people still to this day, for example, who believe that AngularJS powers Youtube's desktop site.

I applaud the efforts taken here, more than I've ever done, and it looks good. But wasn't there big talk of Ember's (JavaScript's) poor(er) performance on Android devices recently? It seems like this tech would be prime for Android users. I don't know if the performance is bad from a usability standpoint or just a pure numbers via specs point of view.

My guess is that it just opens the door for people who would know how to contribute to that codebase.

I also read that as kind of weird. Who is their target audience really...