Re:Once-starving GnuPG crypto project gets a windfall. Now c...
by gaius on Saturday February 07, 2015 @11:07AM
(#9014329)
One wonders why this fancy professor doesn't assign some students to contribute some patches.
Re:Once-starving GnuPG crypto project gets a windfall. Now c...
by iso-8859-1 on Saturday February 07, 2015 @05:35PM
(#9015566)
What does "contribute" mean? You can't make the maintainer accept, even if it's actually a good patch. How could this ever be fair?
Re:Once-starving GnuPG crypto project gets a windfall. Now c...
by raverbashing on Saturday February 07, 2015 @04:53AM
(#9013575)
Code is much more easily written than read, so there's that as well.
Add in some personal preferences and you can easily find someone calling "good code" crap
Reading that reminded me of some comments[1] made by the author of ObjectivePGP, a very recent effort to create an OpenPGP compatible Objective-C library:
> Today I regret that I have not made any notes during programming, so that I could now quote all my moments or doubt, all WTF? instances (I think that some of them are still present in source comments). Many sudden turns of events, lots of dead ends and a massive amount of uncertainty await for the person implementing this protocol. Now I understand why OpenPGP does not have many implementations — the protocol itself is simply quite difficult to implement.
and
> Now, with all I have learned during the time I spent working on it, I would have written the library in an entirely different way. ... I have even made a note in my TODO “Need to rewrite the whole thing!”. This is true, but if I keep on rewriting it all the time, I will not finish anything else.
[1] http://blog.krzyzanowskim.com/2014/07/31/short-story-about-o...