That's why the idea, still pushed as some collages "if you know one coding language, you know them all" is so stupid. In the real world you're not a "X language" developer. If you want to be really good/charge a lot you have to be "X framework" developer.
It's insane how quickly and well one can code when you really "get" on the mainstream frameworks. The designers really did a fantastic job. But it takes a while to learn.
Later when I learned React, I noticed there already were a couple if concepts that I saw before such as lifecycle methods, to the point I could guess what other lifecycle methods React might have.
Once you are on your fourth framework, while only knowing one well, it will feel all the same. At least it does to me.
The questions I ask are:
- what is the preferred way of working with this framework?
- what constitutes fighting against a framework?
- what concepts look a lot (or are identical to) concepts in other frameworks?
If learning is still difficult:
- who wrote a good beginner book?
When I was learning React, I read The Road To React in a few days, then made a small project, then an actual project.
When I really got serious, I had a lot of code already written that I reused as boilerplate/template code and would simply alter it and expand where necessary, learning more advanced concepts on the way.
YMMV
I'm looking at Golang based frameworks my self. I love it as a language and try to use it for everything :-)
Looking for a simpler framework often starts with sacrificing some of the problems you want to solve (or didn't realise were being solved by the frameworks you're considering). Maybe I'll make a website for sorting frameworks based on more personal concerns like "on-ramping complexity" and "amount of learning required to be productive". Obviously subjective but maybe helpful.
Any advice on this front? Is it just a case of using, using, using and eventually it'll all click?