3 ms·
I'm glad Zope lost, and that has nothing to do with Python. Zope was just a morass of over-complication. I remember buying the zope book sometime in the early
by andrewvc 16y ago
I'm glad Zope lost, and that has nothing to do with Python.
Zope was just a morass of over-complication. I remember buying the zope book sometime in the early 00s.
I was initially impressed with the completeness, but found it to be overly-complex and ugly to work with. Rails + Django happened for a reason.
Now, I haven't played with it in maybe 8 years, but I'd say pre-rails it was just not as elegant.
- rbanffy 16y agoI see you met Zope 2. There is still a lot of it under Plone. Neither Rails nor Django appeared on the radar before Zope 3 and Zope 3 is much a nicer platform than 2 (they applied a lot of lessons learned when making it). Grok is even more interesting, as it brings the convention over configuration to Zope 3 (Zope Corp does a lot of government contracts where, I assume, XML configuration files were mandated by clueless PHBs) Also, had Zope been more successful at that time, it would have captured a lot of space that's now owned by Sharepoint and EJB messes.