> or you end up writing one ad hoc using your libraries. I hear this argument a lot, but I don't think it really ends up working that way. You build an applica

> or you end up writing one ad hoc using your libraries. I hear this argument a lot, but I don't think it really ends up working that way. You build an application with some abstractions, not a framework. The difference is that the code you write does what you need, and doesn't need to support a bunch of different use cases. When you need to change it, you can, without worrying that you're breaking someone else's use of it. And because you only need to support the one application, you can make it as simple as it can be to support that application.