The history and future of Python web development. A talk given at PyCon Argentina and PyCon Brazil, 2009.

1. Snakes on the Web:
The history and future of Python on the web
Jacob Kaplan-Moss
http://jacobian.org/TO
http://www.flickr.com/photos/kejhu/3751877257

2. Web development sucks.

3. “
How can I make this
suck less?
”

4. 1. What sucks now?
2. How will we fix it?
3. Can we fix it with Python?

5. In the beginning…
http://www.flickr.com/photos/tonythemisfit/2904911703

6. Hand-rolled HTML
“The Stone Age”

7. The Stone Age
http://www.flickr.com/photos/schoschie/3421072476/

8. Suck.

9. “ What if we
didn’t have to write
HTML by hand?
”

10. CGI
“The Bronze Age”

11. Suck.

12. “ How can we
make CGI better?
”

13. (Not really a big question.)
http://www.flickr.com/photos/randomurl/446209957/

14. PHP
“The Iron Age”

15. Same idea, (slightly) better tech.
http://www.flickr.com/photos/jerhoyet/2377140741

16. Page-oriented
http://www.flickr.com/photos/just_jump/2972461681

17. “
“What if we thought of
these as applications,
not pages?”
”

18. Frameworks
“The Industrial Revolution”

20. The modern
web framework:

21. High-level
http://www.flickr.com/photos/nikonvscanon/2128705916

22. Application-oriented
http://www.flickr.com/photos/joelaz/2868356069

23. http://www.flickr.com/photos/ppdigital/2329405081/
Large building blocks

24. http://www.flickr.com/photos/jasephotos/2913135232/
Rapid development

26. http://www.flickr.com/photos/nattu/1190083977
Fun!

27. What’s next?

28. What sucks?

29. Interoperability sucks.

30. Frameworks: good.
http://www.flickr.com/photos/amberandclint/3266859324/

31. Lock-in: bad!
http://www.flickr.com/photos/striatic/2191404675/

32. Rule 1:
Don’t piss off your users.

33. Software becomes
domain-specific.

34. Cede control gracefully.
http://www.flickr.com/photos/aidan_jones/3575000735

35. Framework inter-op:
http://www.flickr.com/photos/kpwerker/421386062/

36. Django’s not helping.
http://www.flickr.com/photos/mafleen/1694900141/

37. WSGI sucks.
http://www.flickr.com/photos/jacobian/408227408

38. Rack’s better.
http://www.flickr.com/photos/lependu/3563742168/

39. Gateway ≠ API

40. Inter-language
inter-op:

41. VMs, Proxies, SOA, ROA, …

42. Gateway ≠ API !

43. http://www.flickr.com/photos/vgm8383/2381791019/
This’ll be hard to fix

44. Disparate,
mostly volunteer
communities.

45. Little overlap.

46. Rich applications suck.

47. HTML 5

48. The best thing to
happen to web
frameworks?

49. Current frameworks don’t fit.
http://www.flickr.com/photos/oskay/156280584/

50. State of the art:

51. 1. Parallel MVC stacks
Lots of work to keep in sync.

52. 2. Coupled frameworks
(GWT, Cappuccino, SproutCore)

53. ☹

54. 280slides
Create beautiful presentations, access them from anywhere, and share them with the world. With 280 Slides,
there's no software to download and nothing to pay for – and when you're done building your presentation you can
share it any way you like.

55. 280 Slides:
a site so complicated it needed a new language!

56. Python?

57. Deployment sucks.

58. Writing the app is easy…

59. The rest is hard!

60. • API Metering • Distributed Log storage, analysis
• Backups & Snapshots • Graphing
• Counters • HTTP Caching
• Cloud/Cluster Management Tools • Input/Output Filtering
• Instrumentation/Monitoring • Memory Caching
• Failover • Non-relational Key Stores
• Node addition/removal and hashing • Rate Limiting
• Auto-scaling for cloud resources • Relational Storage
• CSRF/XSS Protection • Queues
• Data Retention/Archival • Rate Limiting
• Deployment Tools • Real-time messaging (XMPP)
• Multiple Devs, Staging, Prod • Search
• Data model upgrades • Ranging
• Rolling deployments • Geo
• Multiple versions (selective beta) • Sharding
• Bucket Testing • Smart Caching
• Rollbacks • Dirty-table management
• CDN Management
• Distributed File Storage http://randomfoo.net/2009/01/28/infrastructure-for-modern-web-sites

61. Lots of pieces
http://www.flickr.com/photos/restlessglobetrotter/448362507/

62. Huge opportunity
http://www.flickr.com/photos/nuclearsummer/2665337803/

63. Python’s been a very
good glue language…

64. It could be again.

65. Scaling sucks.

66. Web audiences

67. Complexity

68. Traffic

69. Generic doesn’t scale.

70. Generic Specific
Simple
Complex

71. Specific
Generic
My first blog
Simple Complex

72. Specific
Generic
Public launch
My first blog
Simple Complex

73. Specific
Average site
Generic
Public launch
My first blog
Simple Complex

74. Specific
Twitter
Average site
Generic
Public launch
My first blog
Simple Complex

75. Specific
Twitter
Frameworks
Average site
Generic
Public launch
My first blog
Simple Complex

77. Most sites aren’t big.

78. http://www.flickr.com/photos/b-tal/163450213/
What do we do?

79. Concurrency sucks.

80. All roads lead to multi-core.
http://www.flickr.com/photos/marc_buehler/3053243413

81. I’m scared.
http://www.flickr.com/photos/amatuer_44060/2831112854/

82. Nehalem

83. UltraSPARC T2

84. 128 hardware threads

86. http://www.flickr.com/photos/daninrgb/3406117892
Ted thinks we’re screwed

87. StartServers 128

88. I don’t think so.

89. Lots of exciting work
in concurrency today:

90. Actors
STM
Persistent data structures
Dataflow
Tuple spaces

91. Ted Leung,
A survey of concurrency constructs
http://tinyurl.com/mmbqe6

92. Scala
Erlang
Clojure
Haskell

93. Python?

94. Unladen Swallow?

95. No more GIL!

96. No more GIL?

97. Better threads.
http://www.flickr.com/photos/splityarn/3469596708/

98. Threading sucks.
http://www.flickr.com/photos/sillydog/9844703/

99. I want actors!
(Or STM, or whatever.)

100. Help!
http://www.flickr.com/photos/zaia/3475695085

101. 2020

102. I want to be
using Python!

103. Let’s make Python
kick ass in 2020.

104. “ Good software
takes ten years.
Get used to it.
— Joel Spolsky
”
http://tinyurl.com/ca4pr

105. So we need to start now.

106. 1. Better inter-op.

107. WSGI 2

108. Django needs
to do better.

109. We need leaders.
http://www.flickr.com/photos/salimfadhley/26306549

110. http://www.flickr.com/photos/psd/3649586425/
A BDFL?

111. 2. Get in front of HTML 5.

112. 3. Rethink web
development, again.

113. Pages

114. Applications

115. Sites

116. Full deployment stack,
highly integrated,
centered around WSGI 2?

117. Yes, please!

118. 4. Scale from day 1.

119. Be skeptical.
http://www.flickr.com/photos/colorblindpicaso/2747637336

120. Plan to be replaced.
http://www.flickr.com/photos/taurusaficionado/2099239684

121. Holy crap please give
me better concurrency!

122. Thank you!
Me: Jacob Kaplan-Moss
This talk: http://jacobian.org/TO
Email: jacob@jacobian.org
Twitter: @jacobian