Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I never got the point in these kind of questions anyway. I would never ever learn a framework until i need it because i come into a project where it is used. And then it's settled which one to learn. Greenfield projects are seldom and even when you get in it you won't be the one deciding which technology to choose most likely.
-
I agree with the gist.
But I don't see how your question "I want to learn framework A - should I learn B or C first?" will help in any way. Not entirely sure why would need B or C before learning A...and either way that question will give you similar responses; fans of B will vore for B.
And from my own experience us devs are terrible at suggestion paths for learning. Given two people who learned C++ first and then Python, it just feels random if they suggest taking the same journey or not.
Important thing I learned is not to listen to devs who suggest to learn a framework because its pointless
If i ask should i learn react or angular, some will say angular some react, and both have valid arguments why
When i branch to react and ask if i should learn nextjs or nuxtjs the same thing will happen
No matter if the arguments are valid or not people will prefer a framework they have been biased towards
All frameworks have cons and pros there is no such thing as "the one" perfect framework
No matter how framework is good people will always find a reason to take a shit on it
So from now i wont ask IF i should learn framework X, I'll ask for the order in which to learn it
For example i Know i want to learn A for whatever reason, should i first learn framework B or C?
I dont need your subjective opinion to tell me how B or C sucks and i should do D instead of A
rant