Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Functional web development with Git(Hub), Heroku and Clojure

4.373 Aufrufe

Veröffentlicht am

Presentation from Atmosphere Conference in Poznan, Poland.

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

Functional web development with Git(Hub), Heroku and Clojure

  1. 1. Functional webdevelopment with Git(Hub),Heroku and ClojureJacekLaskowskiPoznań, Polska, 13.05.2013@JacekLaskowskiblog.japila.pl
  2. 2. Don’t forgeta picture
  3. 3. Don’t forgeta pictureSmile, please :-)
  4. 4. The GoalShare a platform todevelop your skillsand have your workavailable to the public
  5. 5. PLAYGROUND• GitHub• Collaboration, review, and codemanagement Platform• Heroku• Cloud Application Platform• Clojure• Functional Programming Language
  6. 6. Learnin’andhaVin’ FUN!
  7. 7. Learnin’andhaVin’ FUN!Always!
  8. 8. Learnin’andhaVin’ FUN!Always!http://www.flickr.com/photos/lauraprevost83/
  9. 9. GitHub
  10. 10. My GitHub
  11. 11. My GitHub
  12. 12. My GitHub
  13. 13. My GitHub
  14. 14. My GitHub
  15. 15. My GitHub
  16. 16. How to GitHub
  17. 17. GitHub :: Watched Repositories
  18. 18. GitHub :: Notifications
  19. 19. GitHub :: Project page
  20. 20. GitHub :: Project Graphs
  21. 21. GitHub :: Project Contributions
  22. 22. Heroku
  23. 23. Heroku Dashboard
  24. 24. Heroku :: Librarian-Clojure
  25. 25. Heroku :: Project Activity
  26. 26. • Functional ProgrammingLanguage• Pure functions...whereverpossible• Immutable data structures• ExpressionsClojure
  27. 27. Why Clojure (1)
  28. 28. • “Learn a new language everyyear” @PragProgWhy Clojure (1)
  29. 29. • “Learn a new language everyyear” @PragProg• New (idioms)Why Clojure (1)
  30. 30. • “Learn a new language everyyear” @PragProg• New (idioms)• (Perhaps) coolWhy Clojure (1)
  31. 31. • “Learn a new language everyyear” @PragProg• New (idioms)• (Perhaps) cool• Fresh (undoubtedly)Why Clojure (1)
  32. 32. • “Learn a new language everyyear” @PragProg• New (idioms)• (Perhaps) cool• Fresh (undoubtedly)• Java interop availableWhy Clojure (1)
  33. 33. • “Learn a new language everyyear” @PragProg• New (idioms)• (Perhaps) cool• Fresh (undoubtedly)• Java interop available• More?!Why Clojure (1)
  34. 34. Why Clojure (2)http://www.flickr.com/photos/karmaowl/
  35. 35. Why Clojure (2)http://www.flickr.com/photos/karmaowl/
  36. 36. Why Clojure (2)http://www.flickr.com/photos/karmaowl/
  37. 37. Functional web development
  38. 38. • Request = a mapFunctional web development
  39. 39. • Request = a map• Request processing = afunction manipulating the mapFunctional web development
  40. 40. “Functional” request
  41. 41. “Functional” requesthttp://localhost:8090/
  42. 42. “Functional” response
  43. 43. “Functional” response
  44. 44. “Functional” response
  45. 45. Functional Librarian-Clojure
  46. 46. • Dynamic web applications withClojure and Ring - part 1http://jaceklaskowski.pl/wiki/Dynamic_web_applications_with_Clojure_and_Ring_-_part_1• Clojure w aplikacji webowej zCompojure oraz Ring i Hiccuphttp://jaceklaskowski.pl/wiki/Clojure_w_aplikacji_webowej_z_Compojure_oraz_Ring_i_Hiccuphttp://jaceklaskowski.pl/wiki
  47. 47. QuestionS?JacekLaskowskiPoznań, Polska, 13.05.2013@JacekLaskowskiblog.japila.pl

×