JavaScript Fatigue or My History with Web Development

Re:JavaScript Fatigue or My History with Web Development by mercurysmessage on Tuesday June 27, 2017 @08:29AM (#14644753)

I never understood the craze over React. I tried it, and I didn't like it. It may work for Facebook's use case, but to me it looks like a lot of people are unnecessarily rebuilding their front ends with React just because it's hot.

[ Parent | on HN ]

Re:JavaScript Fatigue or My History with Web Development by sotojuan on Tuesday June 27, 2017 @08:38AM (#14644799)

A lot of our industry hires based on buzzwords. For web developers, it pays to have React experience in their resume. Doesn't matter if the app they built didn't need it at all.

[ Parent | on HN ]

Re:JavaScript Fatigue or My History with Web Development by weka on Tuesday June 27, 2017 @09:57AM (#14645394)

Depends where, though. I'm based in the South, Alabama, and most of the jobs here want C# or Angular (1x... specifically). I rarely, rarely see React mentioned.

Of those who want JavaScript experience, it's usually followed with "Do you have any .NET experience?"

[ Parent | on HN ]

Re:JavaScript Fatigue or My History with Web Development by sotojuan on Wednesday June 28, 2017 @02:31PM (#14656935)

Yeah same back home in Texas (Houston, not Austin). NYC and SF are different stories :-)

[ Parent | on HN ]

Re:JavaScript Fatigue or My History with Web Development by amackera on Tuesday June 27, 2017 @11:11AM (#14646095)

Facebook's use case happens to mirror a great deal of web products currently.

[ Parent | on HN ]

Re:JavaScript Fatigue or My History with Web Development by mercurysmessage on Tuesday June 27, 2017 @12:01PM (#14646619)

Certainly not in scale.

[ Parent | on HN ]

Re:JavaScript Fatigue or My History with Web Development by amackera on Tuesday June 27, 2017 @01:40PM (#14647484)

That's true, but React doesn't directly deal with those problems (and certainly not the parts specific to Facebook).

[ Parent | on HN ]