What Zope did wrong (and how it's being fixed) Lennart Regebro http://regebro.wordpress.com/ PyCon 2008, Chicago

Zope did most things right

Python

A hierarchical in memory transactional networkable schemaless object oriented logging database with orthogonal persistency and undo.

Security focus

Fine-grained access control

User management

Internationalization

Unicode everywhere

DTML / ZPT

Plugin architecture for code reuse

Component Architecture

Through The Web Development

What Zope 2 did wrong

Through The Web Development

The ZODB pile of scripts

ZClasses

Disk-based products

Development dead-ends

Zope became a ghetto

Didn't play with others

Big monolith

Magic attributes and methods

Backwards compatibility forever

Badly documented

Never ends Starts off easy

Development dead-ends Ghetto Magic Loads of old cruft No docs

Zope 3!

No more dead-ends No magic attributes and methods Managed evolution No ghettos Much better docs

Death by abstraction

A conspiracy on the hard disk

Ugh... Phew...

Zope 2+ Zope 3 = Five

Never ends Starts off easy

Ugh... Phew...

2 + 3 = Five Ugh... Argh!

Low entry treshold and all the power of a big framework without dead ends?

Low entry treshold

and

all the power of a big framework

without

dead ends?

Information Manager IT department Site developer Application developer Core developer User Layer Schema driven content types Workflow editors A CMS, ERP or similar Product Layer A Web application server Application Layer API Platform Layer Python Component Architecture Loads of components Framework Layer

How is Zope being fixed?

Eggyfying

Repoze

Deliverance

Grok

Dexterity