Well, I have worked with two of them React and Angular. Now working with React. And the further the project goes, things just get messy, and I mean really messy. The concept of everything should be a small function is in practice not true. No dependency injection(I know you can bolt another library on top of it, but really?). The testing is a pain, it gets harder and harder to test isolated functions. Custom tags, attributes that look like the standards that are documented at MDN but are not. And most info I can find online feels like elaborate propaganda. I mean there is just nothing against React to be found, really nothing. That’s just not possible in IT.
React is awesome. Sure it has problems but what doesn’t? It’s easy to learn and JSX is great. I would try Next.js, Remix.js or just use Vite. Personally I’m trying out CT3A but that’s a bit on the edge (and uses Next). There are a lot of jobs with react out there and it’s a joy to work with imo.
Vue is supposed to be easy but I had a hard time with the initial learning curve. The community seems much smaller too. I have heard good things about Nuxt though.
Angular is robust but the hardest of the bunch to learn based on popular sentiment i’ve heard.
Solid uses JSX and is both much more performant than React while removing several of it’s footguns. You also have WASM frameworks like Leptos that use similar syntax (RSX) while using languages that aren’t JS.
Angular is different from React, totally different. For one it’s a framework. React is a library.
People tend to say Angular is harder to learn then React but I totally disagree with that. I personally found Angular really easy to learn, especially if you look at their documentation at https://angular.io/docs you just need to work through it, step by step.
This is not the same with React, again my personal experience.
In Angular you have common concepts like observables, subscriptions, dependency injection, separation of concern’s, and not to forget functional programming with RxJS. And the documentation that you can find in MDN about html, css, javascript is then also complimentary to it.
Overal I found Angular to be a cleaner environment to develop in. And testing is so much more concise.
Anyhow, don’t focus on one library/framework. I would even say learn the basics like what you can find on MDN, javascript, html, css, typescript. The rest is always framework/library specific. Let the job decide what you are going to learn first. You know programming, that’s great you will learn the stuff they use on the job and in your free hours ;) In my experience you will have to change anyways. For example I have worked at companies, government and private. Where one uses JSP!!!(in 2022, not it was not a government organization) Then Angular, then React.
Doesn’t matter what an internet rando thinks, there are more React jobs at the moment. I’ve only seen Angular used by large enterprises for internal BI apps, which are harder jobs to get.
Honestly, easiest to learn is probably React. That + market share would make me learn that first. Newer frameworks tend to base what they do with ergonomics from React. Even my favorite (at the moment) frontend library, SolidJS, has all their tutorials with references to how you do things in React, and how similar signals work with Solid. Learning Vue, Svelte, all have the same issue; they compare themselves to React to show you how they do things with their library. And it makes sense, for better-or-worse.
And most info I can find online feels like elaborate propaganda. I mean there is just nothing against React to be found, really nothing.
It’s just Stockholm syndrome. Everybody that wants to criticize it is too traumatized to say anything, and everybody stuck with it makes a way to think it’s great.
Add to that the fact that it is great in theory, so nobody without direct experience can criticize, and you get only positive reactions.
Could you elaborate?
Well, I have worked with two of them React and Angular. Now working with React. And the further the project goes, things just get messy, and I mean really messy. The concept of everything should be a small function is in practice not true. No dependency injection(I know you can bolt another library on top of it, but really?). The testing is a pain, it gets harder and harder to test isolated functions. Custom tags, attributes that look like the standards that are documented at MDN but are not. And most info I can find online feels like elaborate propaganda. I mean there is just nothing against React to be found, really nothing. That’s just not possible in IT.
I agree, React sucks. Been using it for years at work.
I’m gonna tell your boss you said that.
Oh he knows 😂
Thank you for the explanation, so do you think angular is better? I want to start doing front-end and I don’t know what to pick
React is awesome. Sure it has problems but what doesn’t? It’s easy to learn and JSX is great. I would try Next.js, Remix.js or just use Vite. Personally I’m trying out CT3A but that’s a bit on the edge (and uses Next). There are a lot of jobs with react out there and it’s a joy to work with imo.
Vue is supposed to be easy but I had a hard time with the initial learning curve. The community seems much smaller too. I have heard good things about Nuxt though.
Angular is robust but the hardest of the bunch to learn based on popular sentiment i’ve heard.
JSX can exist without React; it’s essentially just an alternative syntax for function calls.
(That is, annoyingly, handicapped in the Typescript checker)
Solid uses JSX and is both much more performant than React while removing several of it’s footguns. You also have WASM frameworks like Leptos that use similar syntax (RSX) while using languages that aren’t JS.
Very true! Shouldnt be a point for react i guess. I believe they originated the syntax perhaps? Regardless, I love it (:
Angular is different from React, totally different. For one it’s a framework. React is a library. People tend to say Angular is harder to learn then React but I totally disagree with that. I personally found Angular really easy to learn, especially if you look at their documentation at https://angular.io/docs you just need to work through it, step by step. This is not the same with React, again my personal experience. In Angular you have common concepts like observables, subscriptions, dependency injection, separation of concern’s, and not to forget functional programming with RxJS. And the documentation that you can find in MDN about html, css, javascript is then also complimentary to it. Overal I found Angular to be a cleaner environment to develop in. And testing is so much more concise.
Anyhow, don’t focus on one library/framework. I would even say learn the basics like what you can find on MDN, javascript, html, css, typescript. The rest is always framework/library specific. Let the job decide what you are going to learn first. You know programming, that’s great you will learn the stuff they use on the job and in your free hours ;) In my experience you will have to change anyways. For example I have worked at companies, government and private. Where one uses JSP!!!(in 2022, not it was not a government organization) Then Angular, then React.
Thank you a lot for taking the time to answer. I think I’ll try some of them, so I can make a more solid decision based on what suits me better.
Look at your local job market, where you want to work, or what you want to build to determine what to learn.
No point learning any tech unless it aligns with the problem(s) you’re trying to solve.
Doesn’t matter what an internet rando thinks, there are more React jobs at the moment. I’ve only seen Angular used by large enterprises for internal BI apps, which are harder jobs to get.
Yeah I’m not basing a life choice on a rando, but it can help to hear his motivations. Once I have that I can draw my conclusions.
Thanks for your input too.
Honestly, easiest to learn is probably React. That + market share would make me learn that first. Newer frameworks tend to base what they do with ergonomics from React. Even my favorite (at the moment) frontend library, SolidJS, has all their tutorials with references to how you do things in React, and how similar signals work with Solid. Learning Vue, Svelte, all have the same issue; they compare themselves to React to show you how they do things with their library. And it makes sense, for better-or-worse.
It’s just Stockholm syndrome. Everybody that wants to criticize it is too traumatized to say anything, and everybody stuck with it makes a way to think it’s great.
Add to that the fact that it is great in theory, so nobody without direct experience can criticize, and you get only positive reactions.
deleted by creator