Skip to main content

How to Pretend Zope Doesn't Exist

I'm doing my best to ignore that I just read Well-kept secrets of Zope, which lists all sorts of things I'm interested in seeing developed and how Zope did it. Zope is our Simpson's to South Park's Python community. All of this ORM wild fire and debates about unicode support and web frameworks seem really petty when someone reminds us that Zope, which most of us never really look at, has been doing some of these things for over a ten years. That's practically a decade in software time!

Will I settle back into a comfortable hole in the ground, cover my years, and chant "There's no such thing as Zope" or am I going to bite some pride and surround myself with Zope? The first talk for a CharPy meeting is going to be on Zope, and I'm going to ask a lot of questions about why it gets ignored and how someone really familiar with Python can get into Zope so late into the game. Now, I am not planning to drop everything else. I still think CouchDB has some interesting ideas that I'm pretty sure aren't part of ZODB. I'm also a huge Twisted fan, where it applies. We've had some segmenting problems in Python with Zope and non-Zope, Twisted and non-Twisted and, more recently, Django and non-Django. We seem to be gaining a habit of frameworks that gain a really large following and are really known to those who don't use them, who continually ignore the developments. If Zope and Twisted played together better, both in code and community, would Django ever have even surfaced to fill the gap? Would Rails have been irrelevant?

We need to build some bridges, so who wants to shake hands?


Technorati Tags: ,

Comments

Florian said…
My first python only job was maintaining a zope application for which original maintainers already hat fled the field. I tried to wrestle the thing to a zombie living where it wouldn't missbehave at the soonest opportunity, and failed miserably.

After 6 months of struggling I was at the end of my rope. I kept my job. While wrestling zope a day I started rewriting what we needed by night with the help of turbogears. Then during 2 weeks of x-mas holidays I worked like possessed, and by the first weeks of january I could present a viable exit strategy for me and the company, which would end up with me having a job and the company having an application.

I blame my predecessors (classic), but I also blame zope to no small degree, because I believe that zope lured these people, then encouraged them to be that messy and horrid, and finally made it possible for them to hang on to their jobs much longer then ought to be.

I derive a simple teaching from this story:
1) before the 3rd to 7th personal complete rewrite, any solution you write to a problem domain sucks beyond relief.
2) There is no framework substitute for being an architect for nontrivial applications. Inversly, using a framework to get near the problem domain solution feels good, but dooms your code.

So what now?

Zope bridge Twisted bridge Django and the Age of MegaGigaFrameworks? and that's going to help with either of 1) or 2)? Who're you kidding?

/me *yawns*
Florian is right, though I blame Zope's predecessor (another classic, but true). Zope 2 has this awful way of luring people into a development scheme that's just wrong and completely backwards. Fortunately, Zope 3 (which is what the Well-kept Secrets article is about) isn't at all that way. Unfortunately, it has the same name as Zope 2. Today we know that was a mistake, but can't easily change it now.

We're certainly up for some bridge-building, Calvin. Using Twisted was just one step. We now fully support WSGI, and at EuroPython I demonstrated integrating Zope with PasteDeploy, something that everybody else seems to be using nowadays.

It's good and somewhat healthy to be looking over the fence once in a while, or even be inspired by others, just like we were with Grok (http://grok.zope.org) which takes the "convention over configuration" approach to Zope. That's why I think it's good for the overall community to have other frameworks with other approaches: they provides breeding grounds for new ideas. I think the diversity of Python web frameworks is a strength, not a weakness.
Florian said…
Philip, I spend quite a time contemplating what constitutes these "lures" in software.

It's a complex phenomenon, but a few things stick out. The probability of a lure rises with the complexity a piece of software. The lure probability also rises with how easy it makes it for people who know neither the problem domain nor the solution space to coax it into behaving a bit like the desired solution.

Zope3 goodness'n all, it _is_ still zope, a big mother of framework promising you to solve the most vexing of everyday web programming problems with a passing glance.

You'll forgive me if that still smells overwhelmingly like a lure to me?
Anonymous said…
Wow you are a brain surgeon. They have been doing it for 10 years? That's practically a decade. Can't put nothing past you!!!!

Popular posts from this blog

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Finding "One Game A Month"

I was really excited about the One Game A Month challenge as soon as I heard about it.
For about two years I've struggled in fits and starts to make my way into game development. This hasn't been productive in any of the ways I hoped when I started. Its really difficult to be fairly experienced as a developer, which I believe I am in my day job as a web developer, while struggling really hard at an area in which your experience just doesn't exist.
Its like being a pilot who doesn't know how to drive.

But this challenge provided a new breath to this little hobby of mine. It gave me a scaffolding to experiment, to learn, to reflect on finished projects. I had spent far too much time on game projects that stretched on far past their exciting phases, bogged down by bad decisions and regret.
And it has worked.
I have a lot to learn. I have a lot of experience to gain through trial and error and mistake and discovery. I have a lot of fun to be had making more small games t…

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…