5 ms·

It’s not a language, it’s a framework. You can take any experienced JS developer and make them proficient in either Ember or any framework mentioned in the arti

It’s not a language, it’s a framework. You can take any experienced JS developer and make them proficient in either Ember or any framework mentioned in the article within days. People overexaggerate how difficult each framework is. They’re all front end frameworks made to do one job. Yes, each of them have their own nuances, but nothing that cannot be understood spending few days coding, reading docs and speaking with someone experienced in this particular framework.

tbranyen 9y ago
Completely untrue. I was at Bocoup and we wanted to standardize on Ember. It took weeks to get devs doing the basics in a large app. Ember isn't gone because its misunderstood. Its gone because we can build the same apps using more suitable libs/frameworks, in a fraction of the time, with less code, less magic, and less upgrade burden. Ember sucked at upgrades, even though they tried to make it better.
- csallen 9y ago
  Ember isn't gone or anything close to it.
  - RobertRoberts 9y ago
    Not to be a jerk, but can you provide any links to large sites or apps that use Ember? Again,this is a serious question, as I like to keep tabs on trends for JS stuff like this.
    - _Tev 9y ago
      LinkedIn uses ember, but other than that I have not heard about big examples either.
      - 3pt14159 9y ago
        Netflix, FreshBooks, Apple Music, Square (the Dashboard), many others.
    - CryoLogic 9y ago
      Twitch, Microsoft Store, LinkedIn, Netflix, Digital Ocean
adjkant 9y ago
I'd argue frameworks are their own language built on top of another, but this is all semantics. As far as learning curves, I'm taking the GP's word on Ember's difficulty to learn, but generally as mentioned below, I don't think you can truly learn a framework that quickly. Convention, best practices, etc take time. For example, someone that learns AngularJS in a day could end up using $scope, a practice abandoned for many reasons for alternate methods. So does standardizing devs and dev teams on the same practices. A lot of these things often take mistakes to truly understand, or someone who has seen a lot of them within close proximity. The way people write code for each of these programs evolved though those exact mistakes. A framework can constrain, but there are still plenty of ways to mess up at a high level.

tbranyen 9y ago

Completely untrue. I was at Bocoup and we wanted to standardize on Ember. It took weeks to get devs doing the basics in a large app. Ember isn't gone because its misunderstood. Its gone because we can build the same apps using more suitable libs/frameworks, in a fraction of the time, with less code, less magic, and less upgrade burden. Ember sucked at upgrades, even though they tried to make it better.

csallen 9y ago
Ember isn't gone or anything close to it.
- RobertRoberts 9y ago
  Not to be a jerk, but can you provide any links to large sites or apps that use Ember? Again,this is a serious question, as I like to keep tabs on trends for JS stuff like this.
  - _Tev 9y ago
    LinkedIn uses ember, but other than that I have not heard about big examples either.
    - 3pt14159 9y ago
      Netflix, FreshBooks, Apple Music, Square (the Dashboard), many others.
  - CryoLogic 9y ago
    Twitch, Microsoft Store, LinkedIn, Netflix, Digital Ocean

adjkant 9y ago

I'd argue frameworks are their own language built on top of another, but this is all semantics. As far as learning curves, I'm taking the GP's word on Ember's difficulty to learn, but generally as mentioned below, I don't think you can truly learn a framework that quickly. Convention, best practices, etc take time. For example, someone that learns AngularJS in a day could end up using $scope, a practice abandoned for many reasons for alternate methods. So does standardizing devs and dev teams on the same practices. A lot of these things often take mistakes to truly understand, or someone who has seen a lot of them within close proximity. The way people write code for each of these programs evolved though those exact mistakes. A framework can constrain, but there are still plenty of ways to mess up at a high level.