I disagree. Often if you write your own framework you end up with small, maintainable code that you fully understand and that does exactly what you need. Diffe

I disagree. Often if you write your own framework you end up with small, maintainable code that you fully understand and that does exactly what you need. Different reasons for writing a new framework: 1. sometimes you disagree with the general direction of the available frameworks. Different people can think differently (think for a second about the different TYPES of frameworks available for web development) 2. a lot of times you don't need 100% of someone else's framework. 3. sometimes it's faster to write something than to research available frameworks and read their documentation. Don't get me wrong, I'm not against code reuse. For tedious work (like re-implementing a protocol with a nasty spec) you want to use a library that someone else has developed and tested. For doing crypto you probably want algorithms and libraries that have been well studied and tested. I look at frameworks (not libraries) as examples of how to integrate various libraries and an approach to solving the particular problem. This is good. Take a look at many frameworks and get inspiration. But then feel free to write something that works for you, reusing code where necessary. That's the beauty of open source.