components vs frameworks

40
component

Upload: timothy-oxley

Post on 12-Jul-2015

315 views

Category:

Technology


0 download

TRANSCRIPT

component

•Twitter: @secoif

•Github: github.com/timoxley

[email protected]

•meetup.com/singapore-js

•campjs.com

Tim Oxley

Singapore JSMonday 4th March

nodejs workshopscoming soon

component

say no to invasive frameworks

a world without jQuery?

nodejs-style modules for the browser

do one thing wellunix philosphy

component/inheritmodule.exports = function(a, b){  var fn = function(){};  fn.prototype = b.prototype;  a.prototype = new fn;  a.prototype.constructor = a;};

component/domify

var domify = require('domify')domify('<p>Hello</p><p>World</p>')// => [<p>Hello</p><p>World</p>]

•AJAX•WebSocket•Routing•CQRS•Data Modelling•Data Structures•Dependency Injection•UI Elements•DOM Interaction•Conversion Utilities•Control Flow

•Function Utilities•Date Utilities•Array Utilities•String Utilities•Number Utilities•Math Utilities•Object Utilities•Canvas•Shims•Testing•Styling

•Templating•Audio•Other•MVC•Backbone•Ember•Gaming•Themes

diversity leads to innovation

invest in a framework vs.invest in components

what if component isn’t the perfect solution?

worst case scenario?

frameworks:

vendor lock-in

fragmentation

useless knowledge

useless code

one size does not fit all

frameworks have a lifespan

heavy to pivot

vs components

modular codebase

custom architecture

more decisions

component is just a build tool+ require shim

specify and bundle dependencies

lightweight

isolate complexity

ecosystem agnosticIt’s not just the web anymore

encourage healthy coding practices

easier to pivot

only constant is change

leverage, don’t lean

open source all the things

components = everybody wins

@secoif

Questions?

http://github.com/timoxley