Kind of like "once you learn Rails you are a Rails programmer from then on"?
I agree that if you're doing nothing but fight with a framework it's probably not a good choice for you. Correct me if I'm wrong but you sound like someone who isn't a big fan of opinionated frameworks in the first place.
I think you are right. I have been burnt by enough frameworks both picked by me or others that promise the world ('really easy, just use this framework! here is an example of a thing X that we did for a demo that kind of looks like something you might want to do').
Then as soon as you do something not anticipated or unimplemented yet in the framework you hit a wall and decelerate from 100 to 0 pretty quickly.
I guess a good framework is one that is extensible and straddles the border between a framework and library.
I've definitely been there, too. I think it's one of the risks in using a framework, but like everything you have to weigh the risks against the rewards.
> I guess a good framework is one that is extensible and straddles the border between a framework and library.
I think Rails did a good job with this. It provides opinionated defaults but allowed people to swap in other libraries as they needed.
Basically once you learn Angular you are an Angular programmer from then on. It has its own terminology and way of doing things, I haven't seen the benefit of going that way.
Also looked at its code, founds so much convoluted stuff in that it is a little scary having to run on top of it.