A tale on building cool web services with http://brunch.io and http://chaplinjs.org
Superiorservice-basedweb apps withBrunch and Chaplin
View Slide
@paulmillr
It’s 2012, after allService-based web appsWhy?
MaintabilityService-based web appsCan develop both of them inparallelFrontend decoupled from backend
Speed & costsService-based web appsServer costs decreasedby a factor of 10+Super fast & responsive feel
Dogfooding!Both parts become easier tomaintainService-based web apps
Open-sourceCan open-source front freely(in some types of apps)Service-based web apps
Open-sourceIncreases company reputationGood API usage exampleCloud.appitHubService-based web apps
ProblemsService-based web appsLive reloadCompiling LESS / Stylus / SASS
ProblemsService-based web appsModulesCompiling Coffee / Type / Livescripts
ProblemsService-based web appsLintingTemplatesScaffoldingTesting
SolutionsService-based web appsSome DOM lib a-la jQuery?Some DOM lib a-la jQuery?Nope! Too unmaintainable.
We needService-based web appsGeneratorBuilderTesterScaffolder
Brunchbrunch.io
Brunch6 commandsnew build watchgenerate destroy test
Structure(app)
DeployalOptimization withsimple flagbrunch build --minify
Brunch 1.5component(1) supportsource maps
BrunchAlternativesCodeKitLiveReloadYeoman (grunt)
Chaplinchaplinjs.org
ChaplinWhy backbone?Super lightweight & simpleThe most popularWell-tested
ChaplinBackbone.js has problemsUnusable as an app architecture
ChaplinChaplin solutionsMemory management Forced modularityRails routesMediator(global events management)CollectionViewLayoutControllers(MVP “presenters”)
ChaplinAlternativesAura: sort of differentMarionette: sort of similar
Chaplinv1.0coming soon
Paul Millerpaulmillr.com@paulmillr