Your SlideShare is downloading. ×
0
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Components vs Frameworks
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Components vs Frameworks

312

Published on

Yet another set of slides for yet another talk on Components.

Yet another set of slides for yet another talk on Components.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
312
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Could you live it. How dependent are you on jQuery’s abstraction of the DOM? Learning about raw browser methods and differences between them, which is diminishing, is reusable knowledge, for the mid term. knowledge about jQuery has only limited use and lifespan. jquery is just an abstraction, an extra layer that will disappear someday. components is an investment in the future.
  • Same thing, and there’s no competition, it’s not going to get better.
  • Technology Stacks
  • jQuery vs. MooTools vs. YUI Backbone vs. Ember vs. ??? Minimal Sharing
  • Wasted investment Unlike the serverside…
  • Embedded, Televisions, etc IE handling when just dealing with TV or XBox
  • how many times have you rebuilt an app
  • less guidance less direction
  • compare moving away from components vs moving away from ember
  • modular design shared code
  • More sharing
  • Investing too much doesn’t make sense
  • Imagine if all software was built like this Imagine if photoshop was built up out of a bunch of open source pieces So you could build a new better photoshop or improve the existing one
  • Transcript

    • 1. component
    • 2. Tim Oxley•Twitter: @secoif•Github: github.com/timoxley•secoif@gmail.com•meetup.com/singapore-js•campjs.com
    • 3. Singapore JSMonday 4th March
    • 4. nodejs workshops coming soon
    • 5. componentsay no to invasive frameworks
    • 6. a world without jQuery?
    • 7. nodejs-style modules for the browser
    • 8. do one thing well unix philosphy
    • 9. component/inheritmodule.exports = function(a, b){  var fn = function(){};  fn.prototype = b.prototype;  a.prototype = new fn;  a.prototype.constructor = a;};
    • 10. component/domifyvar domify = require(domify)domify(<p>Hello</p><p>World</p>)// => [<p>Hello</p><p>World</p>]
    • 11. 500+ Componentshttps://github.com/component/component/wiki/Components
    • 12. •AJAX •Function Utilities •Templating•WebSocket •Date Utilities •Audio•Routing •Array Utilities •Other•CQRS •String Utilities •MVC•Data Modelling •Number Utilities •Backbone•Data Structures •Math Utilities •Ember•Dependency Injection •Object Utilities •Gaming•UI Elements •Canvas •Themes•DOM Interaction •Shims•Conversion Utilities •Testing•Control Flow •Styling
    • 13. diversity leads to innovation
    • 14. invest in a framework vs. invest in components
    • 15. what if component isn’t the perfect solution?
    • 16. worst case scenario?
    • 17. frameworks:
    • 18. vendor lock-in
    • 19. fragmentation
    • 20. useless knowledge
    • 21. useless code
    • 22. one size does not fit all
    • 23. frameworks have a lifespan
    • 24. heavy to pivot
    • 25. vs components
    • 26. modular codebase
    • 27. custom architecture
    • 28. more decisions
    • 29. component is just a build tool + require shim
    • 30. specify and bundle dependencies
    • 31. lightweight
    • 32. isolate complexity
    • 33. ecosystem agnosticIt’s not just the web anymore
    • 34. encourage healthy coding practices
    • 35. easier to pivot
    • 36. only constant is change
    • 37. leverage, don’t lean
    • 38. open source all the things
    • 39. components = everybody wins
    • 40. Questions?http://github.com/timoxley @secoif

    ×