Responder: a Familiar HTTP Service Framework

I will take you on a brief your of my new web framework, Responder, and show you the improvements it has over established frameworks, like Flask.

1. Responder: A Familiar HTTP Service Framework Kenneth Reitz
2. Hi.
3. @kennethreitz
6. github.com/kennethreitz • Requests • Responder • Maya • Records • Tablib • httpbin.org • Python-Guide.org • SayThanks.io • 'Import This' Podcast • Em Keyboard • Certifi • Autoenv
8. Pipenv is the porcelain I always wanted to build for pip. It fits my brain and mostly replaces virtualenvwrapper and manual pip calls for me. Use it. — Jannis Leidel (former pip maintainer)
10. Requests: HTTP for Humans
11. Requests is the perfect example how beautiful an API can be with the right level of abstraction. — Armin Roncher (Flask, etc)
13. History Time!
14. 1999: Zope + Plone. - Established Python early-on as a serious contender for web development, used heavily in government. - Python 1.5.2 was released in 1999. - Other community tools, like buildout.
15. 1999: Zope + Plone.
16. The Rest of the World: Classic ASP, PHP, Perl, and CGI Scripts.
17. WSGI 2003
18. 2005: Django. - Sort of a response to Ruby on Rails. - A serious web development framework. - Originally built for a small newspaper in Kansas, it excels greatly at content-driven applications. - Makes a lot of decisions for you (architecture, etc). - Was the de-facto web framework for Python for a long time.
19. 2006: Pylons. - Took the energy of Zope + Plone. - A serious contender to Django. - Allowed you to build things with a more component-oriented architecture than Django.
20. The Rest of the World: The Classics + Ruby on Rails.
21. 2007: Webob
22. Honorable Mention: Pyramid. The reasonable alternative to Django.
23. Flask. - Everyone’s favorite framework. - Started out as an April Fool’s joke (denied). - “a single file” - Directly inspired by Ruby’s Sinatra. - Grew on popularity due to user-friendliness. - Simple API presented; rarely need to reference the documentation when using it.
24. The Future 2019+
25. vs. Flask Django Choosing your next project’s web framework…
26. Less necessary than you think. Webockets? Sever-Sent Events (SSE).
27. Django Channels Falcon Hug
28. ASGI
30. Responder Intentions… - Include Requests as a standard HTTP client. - Base the Request/Response objects very similar to Requests’ own objects. - See if anyone is interested (they seem to be). - Take ourselves seriously. - Make “the world’s best web framework”.
31. DEMO (Q&A)
32. Thank you!