Exploring Front-End Frameworks

Part II

Objective

"More productive out of the box."

 

  • Convention over Code
  • Stability without Stagnation
  • Wholesale Front-End App

Ember

Meteor

"From idea to execution, faster."

 

  • Universal JavaScript
  • Rapid Prototyping
  • Wholesale Application

Past & Future

December 2011

 

  • Open-Sourced Stack
  • 6 Week Release Cycle
  • Guides and Docs By Version

Ember

Meteor

July 2012

 

  • Open-Sourced Platform*
  • YCombinator Startup
  • Guides and Docs By Version*

Inner Workings

Ember

Routes:

Control current state and data context

Models:

Instance of a data structure defined by route

Templates:

HTML displayed by route with bound data

Components

Reusable building block of data and logic

Services

Control long term state

Meteor

Collections:

Data persistence and reactive binding

Server Code:

Publish collections, private methods

Client Code:

Set up templates, subscriptions, and events

Templates:

HTML displayed by client code with bound data

Packages:

Add on Routing or User Management

Tooling

  • Create a new project
  • Generate code
  • Serve locally
  • Run tests
  • Build for distribution

Ember

Meteor

  • Create new project
  • Serve locally
  • Manage packages
  • Run linter or debugger
  • Interactive Node and Mongo shell
  • Manage platforms
  • Build for distribution
  • Deploy to production

Asset Management

Using Broccoli and Ember-CLI

 

  • Raw Assets
  • CSS or CSS Preprocessors
  • Compiled JavaScript
  • LiveReload
  • ES6!

Ember

Meteor

Using copious amounts of wizardry

 

  • Static Files
  • CSS or CSS Preprocessors
  • Compiled JavaScript
  • LiveReload
  • Manages packages, too

Time For Demos

Questions?

Thanks for listening!

@zachfedor

Exploring Front-End Frameworks: Part 2

By zach fedor

Exploring Front-End Frameworks: Part 2

A lightning talk comparing EmberJS and MeteorJS

  • 486
Loading comments...

More from zach fedor