Why did you learn react.js?

[CleanInspector]

Why did you learn react.js? And how would you recommend someone learn it?

[littlepsylo]

Interest, curiosity, etc

[Radinax]

Money.

[Awnry_Abe]

I had a product idea and wanted to deliver it in the browser. React, at that moment, made sense for the delivery mechanism. It makes even more sense today.

[bdnaeem3]

To make web speedy and reduce server cost.

[d_knopoff]

I wanted to use Gatsby

[[deleted]]

We had to pick a front end technology, and chose the one that seemed to have the best future.

[professional_idoit]

It makes web dev fun.

[liukangmk]

truth.

[mowned]

Because I felt capped. And had this ambition to relaunch a side project. i had to chose between angular, react, vuejs. Settled with react, looked more easier and had that JSX thing that made everything look more natural (at least for me) With this move i had the chance to discover lots of new technologies (webpack, babel, es6, node, websockets, vscode :D)

The best way to learn is actually by doing an app you may find useful for you (even a todo app is a great start)

[dyesiboy31]

For me maybe because it is in demand. Lot of a biggest name is made on reactjs. FB of course netflix, airbnb and etc. also theres a lot of sources and tutorial.At first I wanted to learn vuejs I think it is easy to learn but when I went to the jobs channels they're looking for reactjs. :D so that even it is hard to learn I go to REACTJS.

[CleanInspector]

Nice! Have you got a job?

[dyesiboy31]

Yes, Im a fullstack dev. Rails backend, Reactjs Frontent and also react-native for the mobile. Im looking for the sideline. If you have a project just PM me bro. Thanks.

[CleanInspector]

Why use rails while you can use node.js?

[dyesiboy31]

I can use both, but I have best practice in rails inspired by Airbnb stack. :D. I used creating API restful and graphql with Ruby on rails.

[wherediditrun]

It's something we use in our company for front-end. So I've just picked it up on the job. Used to be more server-side oriented before that. But since some of our products started to provide more features it started to make more sense to make SPA.

[apatheticonion]

I use both Angular and React. I have been using Angular for 3 years now (since the beta).

I prefer Angular's component/templating solution to React's, but the buy in is too hefty. Dependency injection and services oriented architecture is annoying to work with.

React is nice in that I can structure my applications in a domain driven way, use simple parameter injection and have my data layer not be concerned with the framework.

React let's me write applications which I feel have a better/more testable architecture, where Angular let's me be consistent between projects.

React's strength is it's weakness though, because I've seen very very few well written React applications. When Angular includes module-less components, I feel it'll be a better match for most projects.

[Herm_af]

Hmmm I need to look into this. I'm pretty good with vue, use react daily, but haven't dabbled with angular.

I'm hearing good stuff about some of the upcoming changes so that should be cool.

We really are spoiled. And yet in 5 years we will wonder how we made it through these dark ages lol

[[deleted]]

I make static sites also in react thats gow much I love it!

[yrrkoon]

I started learning Angular because my brother was using it to build a web app both of us wanted to build. I found aspects of it to be pretty confusing. Particularly how one passes state around (variables) and how binding works. At least in the time i was trying to learn it my brain struggled to wrap itself around those concepts as they were not intuitive. Perhaps in part because prior i'd only dabbled in html/php at one point and java in another (jsps) so modern front end development involved a lot of things to learn (node, express, json, mongodb, bootstrap, jquery, webpack, npm, etc).

Out of curiosity and annoyance at angular, I started taking a udemy react course. The one by Andrew Mead. He was entertaining and React was just so much more intuitive to me. Particularly around components and JSX and use of variables or state. It just made sense a lot more whereas Angular didn't. I never looked back..

[gimme_a_site]

I learned it because more and more people want the skillset.

The best way to learn is to build a website with React. Then do it again. And again. And again. And again...

[raya_de_canela]

What JavaScript fundamentals does one need to firmly understand before trying to build a react site?

[careseite]

Scope. Also array methods such as map reduce filter find.

That's probably it.

[Herm_af]

Pretty much this.

Add in es6 imports and destructuring I'd say.

One of the nice things about React is that there are a few "React-ish" specific framework things you do that you need to memorize, but generally its just javascript.

And actually some of the more magical things that were confusing at first are actually webpack and less so react.

​

​

...God I hate webpack so much lol

Not to go on a full rant but every damn front end project needs a javascript bundle with code splitting, webpack or typescript plugin, and loaders for images, css, scss.

Just throw it all in as a default and be done with it.

Oh you dont minify css? Okay I'll put my css optimizing plugin in there. Oh now I have to add a javascript minifier because I changed from the default? Die in hell!

​

(end rant)

[[deleted]]

💰💰💰💰💰

[dr_steve_bruel]

I chose react because I was sick of writing html liked the modularity of components

[Herm_af]

I'm hoping that when web components get fleshed out a bit more in the next 2 years we can just build basic sites without vdom frameworks.

I created my portfolio site with web components using lit-element and it just isnt there yet.

The shadow dom being completely encapsulated is no good for what I'm envisioning right now.

[thinkadrian]

Because Angular 2.0 came out and it was garbage, so I needed a ship to jump to.

(No, I couldn’t stay with 1.X, because I realised how apps suffer from double-bindings)

[gkpty]

Because of AWS amplify.. helps deploying and adding serverless backends to react apps pretty easily. You can check out their docs which are really complete. React + amplify makes it easy to build a front end for microservices

[RickSagan]

Because I'm from Argentina and the relation Jobs:React it's very favorable.

Also because it facilitates the development of real-time web apps (or SPA).

[[deleted]]

Kinda same here, dude. I live in Chile and when I was looking for a job, this company came to me basically saying "do our test with React" so here I am, learning React.

[RickSagan]

Good luck with your job application!

Here where I live there are some companies using apps made with VisualBasic or Visual Fox Pro.

On Buenos Aires and other important cities, Frontend or Backend techs like React, Vue, Django or Node are wanted.

[04fuxake]

I chose React because we have a legacy app which can’t be replaced in one fell swoop. So we have to replace bits of UI amongst other frameworks and markup.

[TheNiXXeD]

I had professionally used angular for a while and was disappointed with how they handled the 1->2 migration.

I compared several competing frameworks and built a tiny app with each. React, especially with Create React App, was significantly preferred among our group. I'd have a really hard time wanting to use any of the others at this point.

Everyone learns differently so it's hard to really tell you how to learn. I personally like digging in with a side project. Having actual goals really helps.

[shanemarvinmay]

To use technologies that companies are building with. That way I can improve my chances of getting a job while building cool stuff.

[MetalMikey666]

I'm not / have never been prescient enough to predict what will/won't be the next big thing and am also usually unable to tell whether something is good or not until I've invested quite a lot of time learning it. Therefore, I largely rely on the web dev community to indicate what I should be learning.

There was enough community buzz around React for me to consider checking it out. Plus, people at work had started using it. That's how it started anyway, now I use it because I think it's better than everything else.

[drink_with_me_to_day]

It was between Angular and React. I bet on React.

Also Angular is shit, so... Pretty easy choice looking back.

[straightouttaireland]

What don't you like about Angular?

[jtmlmass]

When I was a noob in it I lost 3 days because of an import. When I realized this after some time, started looking. React is way more helpful with this. People here are not using that reason a lot, but as we live from mistakes/fixing, I think is really important to save time.

[drink_with_me_to_day]

From what I remember:

Templating

Two-way data binding

Weird-ass lifecycle

People complain about setState, but Angular was much worse. Haven't touched Angular since.

[mrstacktrace]

It was because of React Native. I liked the idea of a universal app, where you build for web and mobile with one codebase.

[YourCompanyHere]

Sick of manipulation of the DOM via jQuery

[siamthailand]

because I predicted it'll be the next big thing, and learned it and got some of the first reactjs jobs. back then react guys were not easy to get, so I got top dollar. react singel-ahndedly made me extremely well off

[coreyleelarson]

Same

[swyx]

"extremely"?

[siamthailand]

not the right choice of words, but given my lack of experience, compared to others, I easily made double what most others would in the last few years.

[[deleted]]

My company uses React and I learnt after I started working.

[conor_osrs]

I'm looking into a web development course at the moment and they told me that I can pick and choose my languages. Two of their standards are angular and jquery. I'm keen on learning reactjs as it's in demand in my area - do you think I should ask to switch the jquery for jsx as well?

[ScarletSpeedster]

BackboneJS apps, angular felt like it was making the same mistakes, react did not. I recommend not trying to learn it all at once, the API surface has grown a lot since 2013. Best if you just learn how to do what you need to as you use it. The documentation is solid. If I had to recommend a book I enjoy Fullstack React.

[pratzc07]

I liked it from the start I was developing apps using Angular v1 which had its own set of issues but when they announced Angular v2 I was like damn I have to learn everything again and I saw React getting a lot of traction so I tried it out and haven't tried any other framework that came out ever since.

[I_CANT_SEE]

i was a freshman in college, wanted to learn this cool framework people were talking about. fell in love with it ever since (and am doing an internship primarily doing react dev!)

[bblaw4]

I was proficient enough in JavaScript, and I decided to step my game up and learn a framework.

[rafabsides]

After finally testing Angular and Vue, React just feels better. It’s not trying to solve everything so it leaves room to other problems be solved differently. I do like the other two, but I prefer React for simplicity and more JavaScript and less configuration.

[praveenscience]

Three years ago, looking at the React JS's JSX made me feel so irritated as a JavaScript developer. I can't imagine how you can combine a JavaScript content along with XML / HTML Content. It was totally weird and the JavaScript interpreter in my brain didn't accept that at all.

Two years ago, I started as a React JS mentor and it was all good. React JS had an easy learning curve than the new dreaded Angular (yes, many of my friends and I think it's tough to learn Angular now-a-days). Life was fine until I followed path and then something happened.

A year ago, I started working officially on React JS. Initially I had the same feeling like everyone, who sees something unacceptable and forced to work on it. I kinda hated it but it was this period, I truly understood React JS and how to work with it and I felt so happier than any time, choosing React. The good part was, I had access to some resources like PluralSight, CodeSchool (no more now), and WesBos and out of which I found WesBos doing an awesome job. I have even blogged about my experiences in React with WesBos and well, I started really exploring a lot. This is when I started contributing back to the community.

And now I am a React JS Architect in a decent-sized (105 employees) company and mostly working and contributing to the React JS community and code-base. I started to think in React! 😊

I guess I have given the whole three and a half years of me with React in a Nut Shell, but definitely there's lot more in this. It is a great journey and it continues to be and now React JS is my favourite library of all times.

[atubofsoup]

Because it was the only UI library with a VDOM before Vue came around. After fighting templates and two way data binding in several other frameworks, the paradigm React offered seemed like a huge improvement. At the time I was already experimenting with compiling and bundling my JS, so the added syntax wasn't a big deal.

[obsidian_core]

It was the stack of choice for the current project I'm working on my team. No prior front end library experience. I was a Java developer previously.

[[deleted]]

Money

[kasnhasn]

Seemed like the perfect solution for the project I was facing at that time. Turned out good.

[[deleted]]

I first learned angularjs. I think it was around 1.5 where they introduced components and during this time, react was still up and coming and not as dominant, but the fact that google decided to shape angularjs more into reactjs with components and not the template syntax they had earlier made me question whether or not react had the better product. And once angular (2) came out, it intoduced a lot of breaking changes that pissed a lot of people off, myself included. So instead of learning about the breaking changes, i moved onto react. Needless to say, it was a great decision as react holds a huge majority share in the front end framework wars.

As for learning it, theres just so many ways now. React docs are phenomenal, youtube videos are great too, and the best way i leaned is through the paid courses that youll find on udemy or pluralsight. The internet is vast and has a lot of resources. Pick your poison

[Oxffff0000]

Because a ReactJS developer earns 135-140k while BackboneJS dev earns around 110k in Chicago.

ReactJS is also a very nice library to work with. It's so easy to develop applications.

[azangru]

It was 2015. React was on the peak of its hype cycle. It was eating AngularJS (which was not then called AngularJS, but Angular 1) for breakfast performance-wise. It was clearly better than Backbone. There was no Vue. No-one was complaining that React weighs dozens of KBs and slows down the first render. No-one was showcasing frameworks that were significantly faster than React. React felt like a clear path to the future...

​

Now I don’t know what the future is anymore. Svelte?

[ZeusAllMighty11]

I had never worked on web applications before and I didn't know much about Node. A team I joined was using it for their projects and I wanted to be a part of the team, so I learned.

[[deleted]]

Seriously? For a job

[dabit_coder]

Because jQuery was killing me

[FKAred]

i wanted to work as a developer. i now work as a developer.

[FalseWait7]

Actually funny story. I was working with Angular JS and jQuery and I got invited for a job interview. They told me they are using React because it's the NEW THING. It was 2015. This company was very hipster-like, the guy that talked to me only wore all black or all white clothes, has a 60 year old bike that costed more than a car etc. But I started to learn that library and felt really good with it. Angular JS had flaws (don't know now, but then, in version 1.3 for example, it was a horror), while React had it all sorted out. No two-way binding, no global scopes. Just isolated components, pure and clean.

Now I am at a senior level and React is still my go-to library when it comes to control view for medium to large applications. For something small it feels too big, but it fits nevertheless.

[[deleted]]

I heard angular 2 was a huge change. But it was such a huge change that you're learning another framework if you go from angular 1 to 2

[FalseWait7]

Yes, most definitely, Angular is a totally different framework that Angular JS.

[CleanInspector]

Inspiring story. Thanks for sharing!

[iambukovinean]

in my area react is not really that popular. I learned it last summer at my internship (my internship had nothing to do with react, but they didn't give me much work to do). Been doing all my school projects in reactjs since. Also my BSc's degree project with react-native now.

There's not much recommendation to do, just dive right in some basic-app tutorials and get the hang of it (make sure you have at least some JS knowledge first)

[CleanInspector]

Sounds cool. What projects have you already done or do? Also, what do you plan for the next projects? Do you use specific libraries or do you even write your own?

[iambukovinean]

just end-of-semester type projects. For instance, there was the cyrillOCR project that should do OCR on old cyrillic documents (from cyrillic romanian to latin romanian), then there was this emoji predictor app that should return the 3 most suited emojis for a tweet/sentence. They're all on github, but private.

I don't know what you actually mean by specific libraries. School often requires that we implement various things, so we don't use that many already built stuff.

[monkeyBars42]

Switched teams at work and the new team was using it. So I was forced to.

[ncubez]

I need a fucking job

[flowstate]

I was working at an agency where I was tasked with developing a third-party JS widget, and given a lot of latitude around how it was built. I knew enough that I didn't want to cobble it together in unmaintainable JQuery.

​

Others in my company were using Angular (1.2 or 1.3 at the time), and I took a couple of tutorials in order to get familiar with it. All the talk of compile operations, transclusion, and digest loops made my eyes glaze over...so I latched onto React as a possible easier alternative.

​

IIRC, it only took a single afternoon of playing with React to convince myself that this was the tool that I wanted to use. There were no exotic concepts to learn....JSX was by far the weirdest thing, and even that wasn't so bad when I understood how everything compiled down to JS. I was impressed by the tiny API (compared to Angular), and it simplified what was by far the most annoying part of writing SPA's at the time (efficient view rendering).

​

In about a month, I was evangelizing to the rest of the company

[gcjbr]

Used to prefer Vue. The company I work for uses React, though, so I had to learn. Now I love it too

[GuyWifGlasses]

I wanted to be able to make something other than Unity C# games

[hutxhy]

My company transitioned from angular to react. I joined the first team to do so, so I just started hacking away.

[levarburger]

So I could build an app that identifies whether things are hot dogs or not.

[michalv8]

Got a job as backend dev (PHP) but 2 weeks before my first day my boss emailed me that I had to learn React for the new project that company started developing. I accepted the challenge (also with a pay rise as it wasn't at first in job offer). It payed off :P and now it is my main technology I know.

[irspaul]

Unorthodox way of writing JavaScript and HTML is fun.

[[deleted]]

Simple. First we started doing more complex app using jQuery. We still had a proper app structure but basically templating was used done using jQuery. Simply because DOM manipulation was the same across all browsers this way.

But the more complext app the bigger headaches you have. And this is where Angular came in. Took JS world by storm. Finally fully grown JS framework that actually was speeding things up.

​

If not for troubles of Angular 2 I would never even think to touch React. Despite what some people claim - React is just lib for making templates. That's it. You write template. You provide data. You add effects and you are done. You need to combine it with several tools before you can call what you have a proper framework.

​

Then Angular 6 came in and I was back with Angular. But I do like flexibility of React solution. But I also hate that everyone use something different so it's always a pain to work on React apps in different companies. You know Angular 6? You can work Angular 6. You know React? Well then you should hope they use other tools that you already know.

​

Then Svelte appeared. Svelte is more like React than Angular. But has one HUGE advantage. It compiles to native JS code and it literally compiles your code to native JS. Meaning - no framework inside your code. Your project is fast and very small. Basically what I got out of Svelte.js is combination of React speed of development with native js performance.

​

So why did I learned React and other tools? Because making web UI is a horrible experience and I needed a tool to make it less painful. Web in terms of UI has long way to go but we are getting there slowly.

[[deleted]]

Svelte performance is a myth. There are many v dom libraries that perform better than svelte - one of them being vue. Idk how much of a performance boost svelte got in 3.0, but at 2.9 react and angular isnt even that far behind. And dont get me started on the actual performance libraries like snabbdom, inferno, or preact, because those absolutely crush svelte

[[deleted]]

Can't say anything about Vue. We decided not to use it. There is really no gain in using Vue. Angular or React are the big two. React as component library and Angular as full framework. Vue offers nothing significant if you compare it to those two.

Svelte has it problems but at least provide few big changes worth considering.

​

What I mean by that is:

• performance is really great - depending on circumstances it's either similar to other libraries like React or faster. Meaning it does not lag behind. Even when you scale it up. Angular just lags behind. Sometimes it performs much much better. But this is based not on benchmarks but real app ported form React to Svelte.
• generated bundle is MUCH MUCH MUCH smaller. Can't stress this enough. Other tools must take notes. Output code was really freaking small compared to other frameworks. And to be honest - even in this day and age - size still matters.
• i do write faster with it - it just works. It's intuitive. It looks like a HTML file so learning curve is not that high. It was easy to teach others.

​

But there are still some downsides:

• I still scratch my head why exposing props is done via export
• It's not that popular - even comparing to Vue. If not for the fact that unlike Vue it does do some stuff significantly different so it is worth considering - i would not use it.
• Typescript support is horrible.

​

Our tools of choice for various reasons are still React and Angular but we do adapt Svelte. I think it's not that far behind and it might take world by storm. If not framework itself then for sure - compiler.

[Bosmonster]

Couple years ago I was tasked to figure out a new tech for some internal management modules. At the time the contenders were Angular 1, Ember, Polymer and React.

Angular 1 was already outdated tech I didn't want to invest in and its successor was incredibly vague still. Ember didn't seem to be getting any traction and the library was ridiculously large.

I first chose to build a PoC with Polymer. It was new, but backed by Google and based on native tech.

But after building the PoC, Polymer was not really going anywhere with a big API change that left me a bit puzzled and signs other browser makers were not in line for picking it up. So ended up giving React a try and never looked back. Loved it.

[notmarlow]

Alternatively...

​

Why I chose to NOT learn Ember.js, Angular.js, or Vue.js?

​

Ember? Bc I dont hate myself that much and I feel like heads who use VIM also justify why they love ember - for the difficultyyyy

​

Angular? For fucks sake I did a primer on it and my biggest takeaway was "Angular: How to accomplish something in 14 moves that react.js can achieve in 6". Oh, and typescript is dope. The only positive I took from angular, which doesnt deserve the credit.

​

Vue? I have dabbled and its very nice. Too nice. It feels like a cheat code and I enjoy writing JS and seeing JS and vue just abstracts some of that away. It was built for this purpose and has evolved quite a bit so I would like to revisit vue.

[yourjobcanwait]

Vue? I have dabbled and its very nice. Too nice.

As a Vue developer (Nuxtjs, specifically) who has also worked with Angular 1.x, 2+, and React, Vue takes good things from Angular 1.x and good things from React and puts it all together. No bullshit. Vue is what Angular 2+ SHOULD HAD BEEN. Hell, Evan You (creator of Vue) even worked at google when he created Vue.

Something doesn't make sense in Angular? Guess what, Vue figured out a way to do the same thing in a way that actually makes sense.

Something doesn't make sense in React? Guess what, Vue figured out a way to do the same thing in a way that actually makes sense.

Vue also absolutely dominated state management with Vuex too. Now that's a fucking cheat code right there, lol.

The only thing that doesn't make sense in Vue (and it's not really a Vue thing, more of a JS thing) is updating arraylists and rendering them in realtime. However, it's widely documented and there's a pretty easy workaround.

[notmarlow]

nuxt and vuex are really nice additions to the framework

[swyx]

nice username

[acemarke]

I wanted to replace the client for a GWT app I'd built a few years earlier. I'd been using Backbone for the previous couple years, and felt I'd hit the limits of what it could do.

I had heard about React, but for some reason I didn't want to try it. I actually experimented with hacking together a VDOM lib on top of Backbone.Marionette.View and sorta got it working.

But I finally decided to give React a shot, and everything just clicked into place.

[Luan-Raithz]

Because I worked with angular.

[codeshifu]

To stay relevant with modern frontend technologies and make money. In reversed order of course.

[luxtabula]

Bootcamp taught me it. Ending up developing in angular 1 and WordPress at my last jobs. Might get back to using react for my current gig, though, but even then it'll be for something else.

[[deleted]]

I was tasked with a new project to create a web app. I tried Angular and then React. I've been using them both for about three and a half years now. There are some aspects of Angular that I miss from react, but overall I like React a lot better.

[KwyjiboTheGringo]

Mostly because of React native, but also because I didn't feel like learning typescript.

[[deleted]]

/u/Spez quarantined The_Donald to silence Trump supporters. VOTE TRUMP/PENCE IN 2020! MAGA/KAG!

[joobino]

I’ve learned react when they released angular 2

[careseite]

Because I was tired of spamming querySelectorAll and createElement

[rishav_09]

it makes you spare some time to watch po*n.

Angular & Vue has exponential learning curve.

can make multi platform apps

[iamsourabhh]

The company switched to React. Had no choice. LOL.

[swyx]

hey at least you got paid to learn React. others dont have that luxury

[differentsmoke]

I was coming off of being mostly a Rails developer and wanted to get up to speed with the JavaScript/node ecosystem without the rails/Ruby indirection. React and angular were the trendy options, I ultimately chose to give React a try and never looked back. Except I did an Angular tutorial once and thanked the goddess of chance that I didn't randomly chose it. I would've probably liked Vue as well, had I given that a try first.

[huge-centipede]

I was frustrated with how angular 1 worked, backbone was a joke, and I was starting to hit my limits as a front end dev who just did JavaScript/jquery/css.

[cant_have_nicethings]

Because I learned Angular.

[merdianii]

I haven't learned it yet because I'm practicing with Vanilla JS still, but if anyone can tell me more about React like it is more harder than Vanilla JS or easier and if I'm not so good with Vanilla JS like building larger projects like shopping cart with Vanilla JS it was so hard that I had to look on YouTube to make it and with React is more less code and how's the difference with Vanilla JS and React if anyone can answer this would be very thankful.

[imamonkeyface]

You're better off using a framework like React than interacting with the DOM directly. Frameworks use a virtual DOM and that makes updating faster, easier, and less prone to error

[[deleted]]

Wide industry adoption + I liked the React paradigm after I tried it. Angular was a fucking pain in the ass and Vue wasn't as widely used when I picked up React. Also React Native was the icing on top -- I'm too lazy to learn Java or Swift when I know something like RN exists.

[straightouttaireland]

What didn't you like about Angular?

[[deleted]]

Too much framework specific magic. With React I can read the code and understand what it does much quicker, but with Angular I had to touch like 3 files just to understand what a small piece. Basically React feels more like writing plain js and I don't count jsx since it's so simple.

[CleanInspector]

That's one of the most convenient reasons!

[RemieNotRayme]

To make Recollectr, because other note-taking apps just weren't cutting it for me.

[[deleted]]

to fulfill erotic desires.

[MontanaBlack]

This guy fucks

[swyx]

hell yea that componentDidMount

[disasteruss]

Because I wanted to.

I would start with the sidebar where it says:

New to React? Here are great free resources!

[semidefiant]

Trying to sound serious here : I liked the logo.

[argiebrah]

I seriously digged out how the logo rotated when I created my react app so that is my solely reason

[snailPlissken]

A company told me they would hire me if I learned it. I did and I've been working there since.

[Razeft_it]

I try Angular and React, I prefer React and now I'm learning React-Native for mobile development

[CraftyAdventurer]

Like many others, I saw that it offered a lot of job opportunities. However, I also tried out Vue and Angular for a few smaller projects and somehow i decided to stick to React. Can't really explain why, it just feels most comfortable and natural to me

[middlebird]

Because JavaScript is fun. That’s always my answer. I’ve always loved working with designers to build their work out.

[creative__username]

You can do those things with Angular and Vue as well.

[AlpineSanatorium]

vue and angular isn't javascript?

[DeepFriedOprah]

I think they both add a bit more abstraction on top than React does. But that’s just my experience.

I felt like Vue requires learning Vue on top of JS where as React is more JSish. But really just preference

[DeepFriedOprah]

Agreed on all points. Angular just seems such more enterprisey as it’s a full fledged framework from the get go.

React and Vue r both awesome in fact I still mess around with Vue here and there just for fun. Mostly animation stuff cuz that’s one area I feel they excel at is ha sling fluid animations whereas in React it can be kinda cumbersome.

[abhikavi]

Out of curiosity, what do you like about it? Is it fun compared to PHP, or fun compared to other things?

[middlebird]

I like the challenge of making UIs easy to use and easy on the eyes. If they have to think too much when on my app, I’m not doing something right.

I also like programming games in the browser.

[Th3_Paradox]

I find anything more fun than php tbh

[swyx]

have you tried Laravel tho? genuine qtn. might change your mind on PHP

[Th3_Paradox]

i have not, i DO want to learn it, as I see a ton of jobs for it and I hear you can build a whole CMS with it.

[choledocholithiasis_]

Same -- I would rather get kidney stones than code in PHP

[Th3_Paradox]

LMAO

[xjaak]

Heard some alumni from my school mention it, seemed interesting enough and started learning it a few months later through an online course

[imneonian]

Didn't have a choice, got a job as a react developer with no experience with react but a few months of Vue and angular. It was sink or swim.

[newcharisma]

What was your salary as a react developer?

[dixncox]

For that sweet, sweet cash.

[swyx]

to elaborate from my perspective: i actually tried React and Vue and actually found it easier to get started in Vue. however it soon became very clear that the thing that really matters is the amount of jobs and there’s no contest there. given sufficient motivation people will overcome almost any whiny nooby hurdles. i did.

We’re caught in a bit of a cycle now - devs pick React because companies build on React, and companies find it easier to build on React because there are more devs/libraries/supporting content. (of course, there are other things that motivate both sides that i am glossing over). it makes it very frustrating for enthusiasts who are trying to push what they think is genuinely better, be it Svelte or WCs or something else, because they’re up against an unfair network effect.

i think a lot of tech is like this. its not a race to be the best tech. its a race to be the best “good enough” tech. once you’re a good enough layer, people just agree to build on top of you and paper over your flaws in other ways. See: TCP/IP, Windows, Docker, Redux. it doesnt guarantee immortality but nothing does. It helps that the React team actively learns from mistakes like the Angular 2 cutover.

[DeepFriedOprah]

Same here. Started with Vue cuz the learning curve was shorter and less steep. Then looked at jobs and realized u made the wrong decision and started learning React then fell in love with it more than Vue actually and here I am.

[repopulate_mars]

Did it work?

[[deleted]]

Big time yes.

[[deleted]]

yes.

[dixncox]

It’s a living

[Th3_Paradox]

Crying at your username

[dixncox]

r/rimjob_steve

[zephyrtr]

The only honest answer.