Untitled #3

david’s thoughts about Django & the future

Ancient History Python better than C++ for civilians

1996: science(& web)

1996

bow beforegreatness

RandomExperiences

mozilla messaging

One of thosewas sexy One fit my brain, my style

From hacking to having fun

How django rocked my world

The original noSQLAwesome CSS ondjangoproject.com

Docs!Small steps

to total addiction

Explained the web to me,Made me feel competent.

Admin UI sexy

Adrian plays guitar,and sings too!

Well-designed for scaling

Django successes you may not know about

ispdb.mozillamessaging.com

addons.mozilla.org (at some point!)

Analysis of that success

•understood the competition

•abstracted common patterns

•made them pythonic

•made it sexy

•made it easy

•confidently and modestly

Time to relax? nope.

In practice, django frustrates too!

Need clientsideanswers too!

Admin UI notreal for my sites

Validation

My needs movedfaster than Django

Migrations

Model rat-hole

Templates & client-side code

Evolutionary Path? always be more pythonic

some years out Storm’s a brewin’

User Experiencedrives the web not technocrats

AJAXIdentity

Realtime Web

noSQL & Django? How do they fit?

Code first,then data

(never model)

Normalization, validation, typing, etc:

YAGNI

Embrace the client Embrace JavaScript

Python vs.Javascript Attention economics are scary

the web is deeper Things look differentoutside the pipe

Possible Future #1 “not so good”

FlashSilverlightGWT...

sexyopaqueclosed

Prepare for success

•understand the competition

•abstract common patterns

•make them pythonic (maybe not Python!)

•make it sexy

•make it easy

•confidently and modestly

Possible Future #2 Will it be Django?

assume:strong browsers

various types of data stores

leverage:JS on server and clientopen web as platform

solve the hard problems:

interactivityprivacyoffline

Mozilla Raindrop Not Django!

I’m hiring

web-devfront-end dev

enjoy the skiing! dascher@mozillamessaging.co