On Mar 2, 2011, at 08:00 , Mark Rejhon wrote: > On Wed, Mar 2, 2011 at 9:14 AM, Kevin Smith <[email protected]> wrote: >> On Wed, Mar 2, 2011 at 1:22 PM, Gregg Vanderheiden <[email protected]> >> wrote: >> requires complexity (Mark's claim was that a prototype of this feature >> took him two days. So double that to get a non-prototype version, and >> double it again if you're allowing for the developers not being >> immersed in this field, round down a bit because you're generous, > > When I release permissive open source code, I save all of you time. > Even in your commercial projects. > Also, that's not 8 hour days -- because I have a full time job and I > only work on XMPP-RTT during my free time. > Also, it took me less than 1 day to do a test rtt without real time > editing. 2 days is with editing capabilities. >
1) Unless the code released for a lot of different platforms and languages, it will not save everyone time; in fact, it will save very few people time, and may actually *cost* more time if the protocol is under specified. 2) Unless the license is "public domain" or something as permissive (e.g. 2-clause BSD), this code will not save commercial projects time. 3) Some of us like our software to go through rigorous testing, for which "2 part time days" quickly turns into (at least) 1 work week. 4) One implementation is not enough for ratification of a protocol. 5) Relying on an implementation to completely document a protocol is not acceptable. - m&m
smime.p7s
Description: S/MIME cryptographic signature
