sahrizv's comments

Thanks for pitching in, jon-wood! Can you elaborate what are the major wins with the GraphQL approach using Absinthe (in contrast to REST) which gives you the "superpower" feeling? This is not a rhetorical question.

I agree. Thanks for your comments!

I agree on that.

Maybe one of these will fit our sensibilities:

"NYPD's actions suggest they can label all mosques as potential terrorism organizations."

"NYPD's actions suggest they have a right to secretly or openly spy on men praying in any mosque in New York."

"NYPD's actions suggest they are overriding constitutional rights of Muslims praying in mosques, in the name of security."

(All of these are straightforward conclusions from the article.)

From the original article from Time: http://nation.time.com/2013/08/28/nypd-designates-mosques-as...

"NYPD lawyers proposed a new tactic, the TEI, that allowed officers to monitor political or religious speech whenever the “facts or circumstances reasonably indicate” that groups of two or more people were involved in plotting terrorism or other violent crime." and

"Doing so allowed police, in effect, to treat anyone who attends prayer services as a potential suspect. Sermons, ordinarily protected by the First Amendment, could be monitored and recorded." and also,

"And under the new Handschu guidelines, no one outside the NYPD could question the secret practice."

While I agree that the NYPD explicitly hasn't labeled all mosques, the laws mentioned above allow them to treat all mosques as potential trrorst organizations. And no one can question them.

That's because the said data framework is still far from being production ready and complete. I fail to see why it is a sad thing. It is actually good for the Ember ecosystem that other options are available even when the core team is forced to distribute efforts on all fronts, leading to a slowly evolving data library.

Mine worked in Chrome 29 after giving it some time after load( ~30 secs)...

The most compelling reason to use Objective-C for iOS development is to make use of the vast array of device-native APIs provided by Apple, most of which are not available to webapps as of now. While you can use PhoneGap/Cordova to wrap your webapp in a native container, and access many native APIs, the process is convulated to say the least. Besides, with Apple releasing new API's(1500 new APIs for iOS 7 [1]) with every upgrade, the likes of PhoneGap cant really keep up with natively available functionality. Performance is another big reason which comes to my mind.

[1] http://www.macrumors.com/2013/06/12/upcoming-ios-7-apis-gami...

I chose Ember mainly for its promise of supporting the creation of large, production level apps, through its robust architecture and well thought out library.

On the other hand, "AngularJS is a toolset for building the framework most suited to your application development." Both Angular and Backbone would have required me to learn other stuff for front end development, which I don't want to do right now.

I wanted a single cohesive framework which would be capable of handling all frontend aspects of a large app. Ember is made for that.

P.S Sorry for the late reply. I'm new to HN and didn't know old threads can be active.

Yeah, same with the ember.js guys. Churning out releases and RCs under such restricted timelines.

This post could well have been written by me as I am also in the same boat as you :-)

Anyways, I have chosen to stick to Django for backend( and Ember for frontend). My reasons mainly are the relative unsuitability and incompleteness of Node when compared to Django. If you are onto learning stuff, and not doing some serious (shippable) stuff, I'd say relish the beauty of JavaScript from both ends.

Let's refrain from frequent comparisons until both of these beasts announce a complete and production ready version.

It would be a great blessing for Django beginners like me if some noble soul(s) could turn this into the go-to project template for Django based webapps (by making Mozilla specific stuff more generic).

I understand the point you are making. The only problem with picking up a relatively less mature/complete framework is that I intend to use it in production. Since I am starting up as a novice, I cannot afford to sacrifice maturity for the high of being on the edge. I realize there's benefit for me in being on the edge as you mentioned( and I would love to play with the newest toy), but in my case, I unfortunately can't do that. Thanks for stopping by! :-)

I was looking for a framework which can handle as much as possible of the configuration, plumbing and any other processes which are involved in web development. I know that is not exciting and causes limitations, but being a novice in this field, I do not want to be messing around with the basics. I rather want to focus on the core business aspects of my venture. :-)

Actually I did give a thought to Node.js/express and more pleasantly, the recent one called Mean.io. Mean.io is especially appealing to newcomers like me because it hides significant complexity in linking up stuff on the node.js platform. However, the only thing which puts me off is the instability/novelty of node and consequent unsuitability for production environments. Django OTOH has been battle hardened, and there is help available if I hit a wall. Not at all to say that the node community is not helpful. It's vibrant and helpful but there are simply too many gotchas yet to be resolved, and more importantly, discovered and I do not want to be the one doing these discoveries, midway through my startup. :-)

Regarding ROR, I'd say I have never even seen the language or the framework. Since I have done previous work in NLP/ML I was inclined to learn python so that I can utilize the huge spectrum of Python based ML/NLP libraries, which I believe Ruby lacks.

I am actually inclined towards Ember.js since the time I was faced with this choice. I just wanted to take the opinion of all the experienced developers here, to back my choice or change it. Thanks for easing the choice. I'll go through the Ember docs. :-)

-To comment on your wish to have “a batteries included framework, which I can use in production”: Ember certainly has a lot of batteries included Thanks for considering those factors. Your reply was very helpful.

Mean.io is especially appealing to newcomers like me because it hides significant complexity in linking up stuff on the node.js platform. However, the only thing which puts me off is the instability/novelty of node and consequent unsuitability for production environments. Django OTOH has been battle hardened, and there is help available if I hit a wall. Not at all to say that the node community is not helpful. It's vibrant and helpful but there are simply too many gotchas yet to be resolved, and more importantly, discovered and I do not want to be the one doing this discovery, midway through my startup. :-)

Thanks for reminding me of the employment aspect! For the popularity, I believe both ember and angular have large communities. I checked the jobs and angular although leading here, is comparable to ember in terms of job opportunities.

By "in the long run" I meant the course of my web app development and enhancement. But I feel happy that there is a consensus on transient utility of these technologies. Community size is a strong factor for me but (un)fortunately both ember and angular have large communities. Thanks a lot for your guidance, esp. the last sentence.