Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Intro to Rails

nambrot
November 12, 2013

Intro to Rails

nambrot

November 12, 2013
Tweet

More Decks by nambrot

Other Decks in Programming

Transcript

  1. Web Page Request Resource -> Find File -> Receive Response

    Internets http://cs.bu.edu/fac/snyder/index.html Gimme the resource that I think should be there <html><head><title>I’m Prof Snyder, ... Here you go, this is what I have Request Response
  2. Internets http://cs.bu.edu/fac/snyder/index.html Gimme the resource that I think should be

    there <html><head><title>I’m Prof Snyder, ... Here you go, this is what I have Request Response Web Page Request Resource -> Find File -> Receive Response
  3. Internets http://cs.bu.edu/fac/snyder/index.html Gimme the resource that I think should be

    there <html><head><title>I’m Prof Snyder, ... Here you go, this is what I have Request Response Web Page Request Resource -> Find File -> Receive Response
  4. Request Resource -> *magic* -> receive response Internets https://www.facebook.com/groups/2613588/members/ Show

    me the members of the group 2613588 <html><head><title>Bu Startups Group Members A list of all the members Web Application Request Response
  5. try to think of your biz idea/prototype in this frame

    -> pwn it in rails Ruby on Rails for RESTful CRUD Web Applications
  6. Rails Response/Request Cycle Model-View-Controller Convention for standard CRUD Operations Internets

    http://localhost/posts/1/comments Gimme the comments of the first post Request
  7. Rails Response/Request Cycle Model-View-Controller Convention for standard CRUD Operations Internets

    http://localhost/posts/1/comments Gimme the comments of the first post Request Controller
  8. Rails Response/Request Cycle Model-View-Controller Convention for standard CRUD Operations Internets

    http://localhost/posts/1/comments Gimme the comments of the first post Request Model Controller
  9. Rails Response/Request Cycle Model-View-Controller Convention for standard CRUD Operations Internets

    http://localhost/posts/1/comments Gimme the comments of the first post <html><head><title>Great post, bla bla bla Here are all the comments Request Response Model Controller View
  10. What makes Rails so awesome? Does it print money? Or

    even bitcoins? “Ruby on Rails does for web application developers what a toilet-installing robot would do for plumbers.”
  11. “I hope to see Ruby help every programmer in the

    world to be productive, and to enjoy programming, and to be happy. That is the primary purpose of Ruby language.” Ruby Matz
  12. • Solid Conventions (over Configuration) • Routing • Database Connection/Serialization/Querying

    (Fuck SQL) • Security • Gem Ecosystem • Great OTB Experience/Heroku Rails is a framework Abstracts away common parts of a Web Application
  13. Rails vs Others Most are inspired by Rails • slightly

    less code, declarative style • larger ecosystem for prototyping components • kinda slow • not so good at realtime-y stuff
  14. Web Apps vs Native/Mobile Apps Good for social stuff, less

    cool for individual, interactive stuff UX: - offline - sensors Open Platform: - develop for one platform, reach everyone - not at the mercy of appstores, no proprietary software, use any tools you want
  15. Web Apps vs Native/Mobile Apps Good for social stuff, less

    cool for individual, interactive stuff Performance UX: - offline - sensors Open Platform: - develop for one platform, reach everyone - not at the mercy of appstores, no proprietary software, use any tools you want
  16. Web Apps vs Native/Mobile Apps Good for social stuff, less

    cool for individual, interactive stuff Performance User Experience UX: - offline - sensors Open Platform: - develop for one platform, reach everyone - not at the mercy of appstores, no proprietary software, use any tools you want
  17. Web Apps vs Native/Mobile Apps Good for social stuff, less

    cool for individual, interactive stuff Performance Not As Cool User Experience UX: - offline - sensors Open Platform: - develop for one platform, reach everyone - not at the mercy of appstores, no proprietary software, use any tools you want
  18. Web Apps vs Native/Mobile Apps Good for social stuff, less

    cool for individual, interactive stuff Performance Not As Cool Easier/Faster User Experience UX: - offline - sensors Open Platform: - develop for one platform, reach everyone - not at the mercy of appstores, no proprietary software, use any tools you want
  19. Web Apps vs Native/Mobile Apps Good for social stuff, less

    cool for individual, interactive stuff Immediate Updates Performance Not As Cool Easier/Faster User Experience UX: - offline - sensors Open Platform: - develop for one platform, reach everyone - not at the mercy of appstores, no proprietary software, use any tools you want
  20. Web Apps vs Native/Mobile Apps Good for social stuff, less

    cool for individual, interactive stuff Immediate Updates Performance Open Platform Not As Cool Easier/Faster User Experience UX: - offline - sensors Open Platform: - develop for one platform, reach everyone - not at the mercy of appstores, no proprietary software, use any tools you want
  21. Web Apps vs Native/Mobile Apps Good for social stuff, less

    cool for individual, interactive stuff Immediate Updates Performance Open Platform API Stability SEO Not As Cool Easier/Faster User Experience UX: - offline - sensors Open Platform: - develop for one platform, reach everyone - not at the mercy of appstores, no proprietary software, use any tools you want