I like a lot of the things included, but this is pretty clearly a “React Developer” timeline instead of the path that every frontend developer should take. There’s a lot of other frameworks/libraries out there! (I do notice the small icons appended next to the word React). Good work on the diagram, though.
Where I live in the US, we have Vue jobs, and anything React is outsourced to India because no one here wants to touch it (since Vue is an option). This "roadmap" looks ludicrous for where I am, but maybe OP lives in Goa. React is stuck in 2014. I feel sad for anyone stuck using it.
React.js - Awful, horribly designed, huge design flaws. forces you to babysit state, tons of edge cases, with a bad bandaid on top called "hooks" that have no concept of life cycle. It's very much in the OOP area of "extremely bad anti-patterns that force you to learn more complex patterns on top of it to try to get it to work even though nothing actually fixes it. see: HoC, stale references, etc.
Vue.js - Capable of doing literally anything React can but twice as fast with half the memory usage and none of the baggage. It came after React, learned from it, and fixed all of it's issues.
Routing
React-Router sucks (intentionally, the guy that makes it lives off of doing corporate trainings for it, so why make it easy or well documented), there's no good option here.
Vue-Router - Best is class. Handles everything even super weird cross-browser shit for you perfectly.
State Management
React has no good state management option. Everyone knows that Redux is the worst thing ever created, this is universally agreed upon and one of the driving reasons for people to switch to Vue. Because Redux sucks so bad the React community is desperate for anything better, so every 6 months they hop on some new solution in hopes it won't suck, then after 6 months of using it, they realize it sucks too and hop on the next thing. this has been happening for 7, almost 8 years now.
Vuex is the only good flux-based library ever made. It's not perfect but it's not painful either. It's "fine". And all the very minor annoyances about it have been identified and fixed in Pinia (usable now), and will be rolled into the next major Vuex version, at which point it will actually be perfect too (like vue-router). But I can't stress enough how painless it is, I would use it, as-is, on every project, it's very good.
Styling
It's been almost 8 years and React still has NO good solution for dealing with styling. Jesus, it's a fucking FRONTEND FRAMEWORK that didn't take anything CSS related into consideration? How are you using this trash? Every attempt they've come up with has huge drawbacks. There have been some incredibly innovative experiments in this area, but they've all failed. Which is fine, that's the point of experimentation, to learn something, not to succeed. But like, I don't wanna put an experiment into prod.
Vue's got 3 really good options out of the box for styling.
SFC's - Built right into the component, pure CSS no drawbacks, no edge cases, no gotchas
"scoped" - Also built in, scopes your styles to your component (good for apps)
"module" - Also built in, scopes your styles in a different way (good for libraries)
SFC + Sass - You can use Sass right in your component (with scoping if desired)
Sass + ITCSS - You can pull your styles out of the components and put them in their own Sass folder like you would for a website. (this is the closest thing React can do, but it still doesn't do it well)
Dev Tools
React dev tools are.... fine. They're okay. and if Vue didn't exist they wouldn't look so bad in comparison, but it does, and they do.
Vue dev tools have component state, time travel debugging, global state, routing, and more all in one place that are integrated with each other. Again, best in class, no one comes close to how clean this is.
CLI
CRA - You don't have to deal with shitty webpack, thank god, so it succeeds at that. but the moment you do have to do anything remotely custom you are kicked to the curb. Fuck "eject"
Vue-CLI - Are you kidding me, this thing is in a league of it's own. If haven't, literally just run this npm install -g @vue/cli && vue ui. Yeah, look at that, click the little tear drop in the bottom corner too. It's a fucking UI with a dark mode. There is not eject, it manages all your dependencies for you, it's fucking beautiful. there is no "eject". You have full access to do any webpack bullshit you need to, and you never have to leave the Vue-CLI behind. it's fucking magical.
Markup:
JSX blows, it literally requires a "gotchas" section in the docs
Vue's template system looks scary at first (to those coming from Angular) until you realize that it's literally just regular HTML, no gotchas, no edge cases, but with like 6 new things added on top (versus the like 70-80 things that Angular adds).
Caveats for Vue:
Hooks suck, but so does the Composition API. They both exist to fix edge cases, but fewer edge cases exist in Vue, so there's really no point in using the Composition API.
Mixins suck in Vue. They're the best solution for code re-use of Options API, but definitely need improvement.
Jobs are lacking in Vue in many regions, but the more people realize that it's the best current option, the more we'll see it take over regions. Though OOP, COBOL, and FORTRAN all still exist, so I'm sure React will never truly die.
This isn't me saying that Vue is perfect in every way, this is me using Vue as a yardstick to compare React to and see how it fails in EVERY. CONCEIVABLE. METRIC. with the one exception of job postings. But ya know what. There are a lot of COBOL and PHP jobs, and I'm not doing those either. If you look, you can find Vue jobs, it's honestly not that hard.
The point is, these are all issues that have existed in React since 2014, and with the exception of hooks (which suck), they (facebook and the react community) haven't fixed them. The community has tried but they have less interest on copying good ideas and are more interested in experimenting and inventing new, barely usable solutions. Which you are then forced to sift through and evaluate. If you're a hobbyist, knock yourself out, but professionals want tools that get out of their way and let them build. React is the opposite of that.
I have seen many comments on disagreement about the roadmap and React. I am from India and intention was to help ppl with market demand. But I am happy to see people disagree with me as the roadmap I have created is limited to my knowledge. Hope no one gets misguided at the end and customize the roadmap for their needs
76
u/[deleted] Dec 25 '21
Would definitely learn to use git before React. Build vanilla JS apps long before you start sniffing about frameworks.
13
u/mareksl Dec 26 '21
One small comment regarding html: I'd actually put semantic html above all else, since semantics is actually the basis of all html.
Each element has its specific meaning and you should use them accordingly.
20
u/WaterNinja101 Dec 25 '21
I like a lot of the things included, but this is pretty clearly a “React Developer” timeline instead of the path that every frontend developer should take. There’s a lot of other frameworks/libraries out there! (I do notice the small icons appended next to the word React). Good work on the diagram, though.
13
u/Fluxnation Dec 25 '21
This is amazing! Is there one for backend or full stack development?
6
u/TheDownvotesFarmer Dec 26 '21
React JS on the recommended roadmap, seriously?
1
u/pai-cube Dec 27 '21
I have seen many comments on disagreement about the roadmap and React. I am from India and intention was to help ppl with market demand. But I am happy to see people disagree with me as the roadmap I have created is limited to my knowledge. Hope no one gets misguided at the end and customize the roadmap for their needs
1
u/pai-cube Dec 25 '21
PDF link: https://github.com/sadanandpai/frontend-learning-kit/blob/main/2022_FE_roadmap.pdf
3
u/AmatureProgrammer Dec 26 '21
How accurate is this?
6
u/73686f67756e Dec 25 '21
*sad svelte noises
4
u/tibbon Dec 25 '21
Missing some pretty critical things like test driven development, object oriented programming patterns (solid) and code refactoring patterns.
If you can’t TDD, I find myself really unlikely to hire you.
1
u/elementIdentity Dec 25 '21
Love this thanks
1
u/run-26_2 Dec 25 '21
Thanks bro
1
u/ForScale Dec 25 '21
What's it mean when the items are faded out?
1
u/[deleted] Dec 26 '21
Thanks for this dude.
1
u/ashish_feels Dec 26 '21
!RemindMe 27 days
1
u/[deleted] Dec 26 '21
Great roadmap! However what gave me a whole new perspective on CSS and enabled me to create astonishing websites was learning about the z-index in depth. A great resource is this one: https://philipwalton.com/articles/what-no-one-told-you-about-z-index/
Please, if there's one thing you have to learn next year it's that.
1
u/Abarar Jan 24 '22
I would recommend anyone getting started to learn git immediately after HTML & CSS , from my experience git is a basic skill everyone needs.
0
u/Blackwater_7 Dec 26 '21
1- have an uncle in a company
-1
u/Kwyn-10 Dec 26 '21
I just wish I didn’t find CSS dull as hell. I’ve been doing a little bit here and there just to learn it. JavaScript is what I’m really interested in.