Re: [Zope-dev] Re: Re: OFS.Application deprecations for Zope 2.10
Chris McDonough wrote: An example of cruft removal that is worthwhile: the help system code has stupid side effects (it writes to an invisible catalog in the ZODB *at startup!*), and people have an alternate way of viewing the help via the filesystem. Apparently nobody actually looks at the help system anyway, because if they did, they'd be complaining that it has content that's something like three major revisions behind. So that's a huge pile of cruft that could be ripped out, which would be a pure win. I dunno, I still find it handy for documentation for sequence.sort and DateTime, which I can never remember... OTOH, I'd like nothing more than to get a do-over on sessions, but I won't get it. They have a nasty API. I'd rip that API out in a heartbeat if I didn't know it would screw lots of people. So I leave it because it's the right thing to do, clean or not. Yeah, with you on this one... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Re: OFS.Application deprecations for Zope 2.10
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm sympathetic to that. Change is hard, though and keeping existing code running is more important to the "Zope brand" than notional API cleanliness, and it's important to pick your battles. An example of cruft removal that is worthwhile: the help system code has stupid side effects (it writes to an invisible catalog in the ZODB *at startup!*), and people have an alternate way of viewing the help via the filesystem. Apparently nobody actually looks at the help system anyway, because if they did, they'd be complaining that it has content that's something like three major revisions behind. So that's a huge pile of cruft that could be ripped out, which would be a pure win. OTOH, I'd like nothing more than to get a do-over on sessions, but I won't get it. They have a nasty API. I'd rip that API out in a heartbeat if I didn't know it would screw lots of people. So I leave it because it's the right thing to do, clean or not. On Jun 14, 2006, at 6:55 AM, Rocky Burt wrote: On Wed, 2006-14-06 at 01:04 +0200, Florent Guillaume wrote: Then the framework never gets cleaned up. I'm actively learning Zope 2 core as much and as quickly as possible so I can become a more valuable contributor. The less "gunk" I have to learn about and understand the more quickly I'll become more valuable. I have to side with Florent on this one and say that there is an implicit goodness about removing "gunk" just because it is "gunk". And "gunk" that was deprecated should be ripe for removal. - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server (blog) -- http://www.serverzen.net ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEj/CH8sgUgRRnf6URAm6EAKCgViLHPC7rczKAmsof/YwJpQbohQCeNRqT Mq1TGhlu5AMNhvLsLKQfls8= =j0fI -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Re: OFS.Application deprecations for Zope 2.10
On Wed, 2006-14-06 at 01:04 +0200, Florent Guillaume wrote: > Then the framework never gets cleaned up. I'm actively learning Zope 2 core as much and as quickly as possible so I can become a more valuable contributor. The less "gunk" I have to learn about and understand the more quickly I'll become more valuable. I have to side with Florent on this one and say that there is an implicit goodness about removing "gunk" just because it is "gunk". And "gunk" that was deprecated should be ripe for removal. - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server (blog) -- http://www.serverzen.net signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
