On 20/10/13 07:02, David Fifield wrote: > It's not that I'm trying to neglect unglamorous development--I'm really > not. This is how I see it: As a software engineer, I am always trying to > reduce risk. Refactoring code reduces risk in the long term but > increases risk in the short term. Sticking with our old busted > duplicated code is risky in the long term, but very predictable in the > short term. We've already done a lot to destablize the code (just by > adding new features), so if possible I prefer not to further destablize > it before trying to build bundles. The risk associated with refactoring > is one I think can be safely deferred for a couple of weeks. > > Does it at least come across that there is some principled reasoning > behind my recommendations? > > I'm fully with you on doing code quality improvements before WebRTC and > transport composition. > OK, I can get along with this. -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev