This post originated from an RSS feed registered with Python Buzz
by Ian Bicking.
Original Post: I'm unhappy
Feed Title: Ian Bicking
Feed URL: http://www.ianbicking.org/feeds/atom.xml
Feed Description: Thoughts on Python and Programming.
Zope and an RDBMS are a horrible combination. It's awkward and annoying for a while, until it becomes unmanageable and horrid. Like, did you know if you get a conflict error from your RDBMS, Zope will retry the entire transaction (i.e., rerun the request)? It would be handy, unless it's not what you want, and if it's not what you want nobody knows what to do next. That's just one of many gotchas when using an RDBMS with Zope.
I would just dive in and change stuff around, but I know I'd just recreate another set of problems, because everything is so damn subtle (read: tricky and likely to break). Zope learning starts out hard, then gets easy after an hour, then gets hard again after another hour, then gets impossible after a week. Or it stays just hard, but you've unwittingly created buggy, unscalable, insecure applications.
All my Zope unhappiness might be okay -- not great, but maybe okay -- if it was just pleasant once in a while. But it's never pleasant, just bearable.
Damn, I'd almost rather work in PHP. Actually I would. That's how much I dislike Zope. At least you get all their crap up front, and you can just work around it.