Take control of your
Front-end
Dheeraj Kumar
Chief Troll Officer
Bang The Table
!
[email protected]
Slide 2
Slide 2 text
–Someone on Twitter
“The question is not if you need a
front-end framework. It’s how
long you can survive before you
realize you need one.”
Slide 3
Slide 3 text
Why do I need a front-end
framework?
Obvious point 1
Obvious point 2
Testing
Obvious point 3
Slide 4
Slide 4 text
How do I realize I need a
front-end framework?
Look at your APIs. Do you even have one?
Is your JS maintainable?
Can you change a part of your front-end without
changing/crashing another?
Slide 5
Slide 5 text
Fast forward a couple of
months, a failed project, and
several unsolvable bugs…
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
–Isabella I
“The distance is great from the
firm belief to the realization from
concrete experience.”
Slide 8
Slide 8 text
Alright, what can I do?
Angular
Ember
Backbone + React
Slide 9
Slide 9 text
Angular
Deceptively low barrier to entry
Documentation
AMD
The magical $scope
Performance
Not a framework
Just like Rails - Writing bad code is really easy
Slide 10
Slide 10 text
Ember
Just like Rails - convention over configuration
Steep learning curve
Performance with HTMLBars
Actual real framework
Writing bad code is difficult
Community-driven, with best practices
Slide 11
Slide 11 text
Backbone + React
React - New hotness from Facebook
Super-fast view layer (Meteor Blaze/HTMLBars/React)
Proven model+routing layer from Backbone
Components made easy
Virtual DOM, DOM Diff, Reconciliation, all that jazz…
Slide 12
Slide 12 text
–You
“It makes sense, but I’m still
confused!”
Slide 13
Slide 13 text
Go, try them out. Spend
an afternoon.
!
You won’t regret it.
The End