↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Why I recommend EmberJS over AngularJS

The author recommends Ember over Angular because Ember’s opinions and conventions make code easier to understand, team practices more consistent, and day-to-day development less fragmented. He also argues that Ember’s versioning lets 2.0 features arrive incrementally in 1.x, while Ember CLI reduces setup and build work.

Reading notes
#

  • AngularJS had been enjoyable for the author because it made advanced user experience, two-way databinding, and unit testing easier.
  • The announcement of Angular 2.0 as a complete rewrite without a clear upgrade path changed his view of the framework.
  • He saw Ember as an alternative worth evaluating when moving to Angular 2.0 would require rewriting Angular 1.x apps.
  • Ember’s opinionated structure initially annoyed him, but browsing a production Ember app helped him understand its code base quickly.
  • He says Ember’s conventions made it possible to understand a large project in minutes instead of hours or days.
  • He says the framework difference did not depend on feature parity, since Angular and Ember can both provide the same functionality to end users.
  • He does not see his choice as simple “shiny new toy” switching, because each framework had benefits over the previous one.
  • Ember’s core team works on production apps that use Ember, and he treats that as an important advantage.
  • He argues that core developers who dogfood the framework are more likely to care about the experience of other developers.
  • He contrasts that with Angular 2.0, where core team members would not feel the pain of rewriting apps from 1.x to 2.0.
  • He says guidance and best practices in Ember are set by people who created the framework, and those rules are built into the framework itself.
  • He describes Angular as offering little guidance, which leads teams to structure apps differently and debate architecture for long periods.
  • He says Ember helps new team members become productive quickly because they can rely on a shared structure.
  • He notes that Ember 2.0 features are being introduced in 1.x releases before 2.0 ships.
  • He gives virtual DOM support and Fast Boot as examples of 2.0-related features already appearing in 1.x.
  • He says Ember CLI reduces the work of adding third-party libraries and generating application scaffolding.
  • He compares Ember CLI’s single-command workflow with the manual steps needed to add an addon without it.
  • He presents Ember CLI blueprints as a way to generate routes, templates, and tests together.
  • He concludes that he prefers a framework that supports its developers and does not leave them facing repeated rewrites.