4 ms·
The reason is probably that it's closely tied to Rails. I don't want to learn Rails, but I keep seeing Ember and Rails mentioned together. Probably the same com
by kowdermeister 10y ago
The reason is probably that it's closely tied to Rails. I don't want to learn Rails, but I keep seeing Ember and Rails mentioned together. Probably the same community is behind them (too lazy to look up).
I don't really know where I have this preconception from, but probably it's not just me.
http://discuss.emberjs.com/t/are-developers-creating-ember-apps-outside-the-context-of-rails/283 http://discuss.emberjs.com/t/are-developers-creating-ember-a...
- lightblade 10y agoEmber has zero ties to Rails. We are using Ember with Java backend. I have seen Ember used with .NET and Go backend. There are even the SANE stack [0]. The only possible tie that Ember with Rails is that it used to bundle ActiveRecordAdapter with Ember data. It is now separated into another project possibly due to this exact reason. [0]: http://sanestack.com http://sanestack.com
- OhSoHumble 10y agoI think that project is still under ember-data? https://github.com/ember-data/active-model-adapter https://github.com/ember-data/active-model-adapter
- OhSoHumble 10y agoThe two are different projects - it's just that they're a popular pairing. I could very well use Ember with Django or Dropwizard or whatever. I picked Rails because the project I'm working on is something that calculates the delta between a Chef implementation and what is in an EC2 environment. Ruby was a natural choice due to a strong library support for both the Chef API (thanks Seth Vargo and friends) and EC2. It was on a whim that I chose Ember. I have heard of it before and how the project took stability a bit more seriously than other JavaScript frameworks so I went for it and was pretty pleased. It was super, super easy to integrate. I think another similar pairing is Vue.js and Laravel and that actually makes me want to learn PHP. I used to do a lot of Code for America work before I got distracted by my career and a desire to move out of my state. When I get back to it, I'll probably choose Rails and Ember just because of how happy I am. Now, if I decided to stop doing operations/systems/devops work... I'd probably take React and other frameworks more seriously.