> A framework, usually, must predict ahead of time every kind of thing a user of it might need to do within its walls. Well, when I'm building something opinio

> A framework, usually, must predict ahead of time every kind of thing a user of it might need to do within its walls. Well, when I'm building something opinionated like something resembling a framework, I usually aim for something that handles 80% of the use-cases, and then make sure that you can go around the framework for the other 20%. Your "thing" should always have a way to get out of the way and fall back to the un-abstracted way of doing things. Then you don't have to predict the future.