Sounds like you're solving different problems than I am. May I ask what kind of problems you're solving, that the same framework works for all of them? Never

Sounds like you're solving different problems than I am. May I ask what kind of problems you're solving, that the same framework works for all of them? Never mind, my question is really just bait, don't answer it. My point is that there's a certain arrogance to watch out for, when we claim that our solutions will work for other people's problems, but we don't really understand what their problems are. I've shared my negative experiences with frameworks, but I can't speak universally. I can only suggest that people not use frameworks, based on the experiences I had. I'm not about to—for example—state outright that someone is doing things wrong just because they don't make the same choices I would make. This is the kind of attitude that I watch out for when mentoring junior developers who think code is "messy" and needs to be "fixed" just because it doesn't match the way they write code. I'm very reluctant to learn any more frameworks because tomorrow's problems seem not to match the frameworks we chose yesterday. Again, this is just my personal experience, and you use different frameworks and solve different problems.