Frameworks can be difficult to learn if they are designed differently from the one you've worked with before. I've been in your position where I was in a team

Frameworks can be difficult to learn if they are designed differently from the one you've worked with before. I've been in your position where I was in a team using our own homegrown framework and was switching to a more widely accepted one. What we ended up using would not be considered an easy to use framework today, but the switch was seamless for us. This was because the framework we switched to worked almost the same way as our homegrown one (at a high level, not at the implementation level). The patterns were the same, the actors were the same, the interfaces between objects were very similar. So my advice is, with ease of learning for YOU being your primary criterion, read about the different frameworks out there now and see which one works closest to what you've been using. Hopefully you've designed your framework on sound patterns and known best practices and finding a similar one wouldn't be too difficult. If you picked ideas from other frameworks to implement in your own framework, maybe you can start with the framework you copied from the most.