Continuing the IMAP analogy, for me to put up fragments if client-side IMAP message caching code would not do any good to anyone who isn't intimately familiar with that specific problem space. Typically the would-be downloader sees "IMAP" and latches on with the hope they will find a tool that will help them sort and filter their mail. But when they double-click on imcache.c they get some strange pop-up dialog from Windows instead of the IMAP email client they were expecting. Avoiding that requires an access filter.
Besides how ridiculous your example might be, *if* it was true it would apply as much to unfinished code as to "ready to ship" code, and would be an argument to *never* release any code. If you don't want to release any code for whatever reason, fine. But don't say "it is because it is not ready to ship" and then make up ridiculous arguments that if taken seriously apply as much to code "ready to ship" as to anything else. As you said, it is your code and you can do with it whatever the hell you like, but if you are going to give excuses for not releasing it at least be minimally intellectually honest. And as I said, if you want to release your code anonymously and not provide any contact email address with it, that is fine by me.
> Plan 9 is the only "open source" project where this kind of ridiculous > practices exist. Why on earth Plan 9 has to be different and drive > everyone around crazy is beyond me. Maybe we aren't trying to solve penis envy?
I'm starting to suspect that maybe nobody cares about the future of Plan 9. uriel
