3 ms·

> In my opinion most of the Great Javascript Fatigue of 2015-16 was caused by users trying to fill in the blanks left by the React team and producing one soluti

by orf 10y ago

> In my opinion most of the Great Javascript Fatigue of 2015-16 was caused by users trying to fill in the blanks left by the React team and producing one solution after another (and quickly abandoning ship as something iteratively better was released). I agree wholeheartedly with this. And it's also why I love Ember, you get templates, routing, data access all working together with minimal configuration. I love Django and part of the reason why is that it's opinionated, and Ember is the same.

k__ 10y ago
I found Ember was much harder to get started with than React. More concepts, it's own CLI and build system, outdated docs. (I used it 2 years ago)
- mcardleliam 10y ago
  2 years ago is decades in the front-end world. If we make decisions today based on the state of things years ago, we'd be screwed.
  - coldtea 10y ago
    And yet nothing much changed in the needs of webapps or in the Javascript language in the past two years. And if we CAN'T "make decisions today based on the state of things years ago", then we're really screwed.
    - mintplant 10y ago
      > And yet nothing much changed in the needs of webapps or in the Javascript language in the past two years. But Ember has likely come a long way in that time - I think this is mcardleliam's point.
      - k__ 10y ago
        For me the creation of ember cli was like admiting their framework didn't work as good as they intended.
        orf 10y ago
        I'm sorry, Ember has come a huge way in 2 years. We've got 2.0, which was a big leap forward, a whole bunch of concepts were refined/removed or changed. Also you're flat out wrong: Ember-cli isn't really anything to do with the framework. You don't need it to write Ember apps, it's just the communities command line tool for managing Ember projects. That's all.
        k__ 10y ago
        This is only theoretically right. Practically, there are Ember modules/extensions/features that require Ember-CLI to work or are a huge pain to work with, if you don't use the CLI... for example animation libraries or glimmer.

by orf 10y ago

k__ 10y ago

I found Ember was much harder to get started with than React. More concepts, it's own CLI and build system, outdated docs. (I used it 2 years ago)

mcardleliam 10y ago
2 years ago is decades in the front-end world. If we make decisions today based on the state of things years ago, we'd be screwed.
- coldtea 10y ago
  And yet nothing much changed in the needs of webapps or in the Javascript language in the past two years. And if we CAN'T "make decisions today based on the state of things years ago", then we're really screwed.
  - mintplant 10y ago
    > And yet nothing much changed in the needs of webapps or in the Javascript language in the past two years. But Ember has likely come a long way in that time - I think this is mcardleliam's point.
    - k__ 10y ago
      For me the creation of ember cli was like admiting their framework didn't work as good as they intended.
      - orf 10y ago
        I'm sorry, Ember has come a huge way in 2 years. We've got 2.0, which was a big leap forward, a whole bunch of concepts were refined/removed or changed. Also you're flat out wrong: Ember-cli isn't really anything to do with the framework. You don't need it to write Ember apps, it's just the communities command line tool for managing Ember projects. That's all.
        k__ 10y ago
        This is only theoretically right. Practically, there are Ember modules/extensions/features that require Ember-CLI to work or are a huge pain to work with, if you don't use the CLI... for example animation libraries or glimmer.