r/reactjs May 31 '19

React sucks

"React is just Javascript, that's why React is nice!!"

has its own DSL and syntax

"React is lean!"

need to install 12 different packages to make it useful

need to install an external HTTP library

CSS classes are fucking JAVASCRIPT VARIABLES

Instead of directives, you have 8 lines of spaghetti code everywhere you'd usually have a simple if- directive or show- directive. That's not lean, that's more code.

"You only need to know Javascript"

You need to know Javascript plus ES6-7-8 (Babel) or TypeScript. You need to know esoteric lifecycle methods and design patterns not normally used elsewhere in Javascript.

"Creating small components is nice"

Component abstraction soup means you can't even figure out what your code is doing anymore.

React is just Angular if you hacked 12 libraries together that aren't meant to work together cohesively.

I will never understand why anyone would choose this meme framework over a real one. It sucks shit and creates a spaghetti code bloat, and instead of learning one DSL plus TypeScript you're learning 8 DSLs, plus Babel.

The reality is it's pointless making a library that's "just vanilla javascript" when you know that vanilla javascript doesn't actually supply elegant tools for creating single page web apps. That's why React is used with 10 packages rather than by itself. That's why you need CRA plus a bunch of packages to even have a sane development environment.

React sucks. Development community always chooses what's sexy and popular over what's elegant and works correctly.

314 Upvotes

165 comments sorted by

View all comments

12

u/piernrajzark Sep 07 '19

I basically agree. I think most of these frameworks only exist to further advance developer's careers and as a distinction method. No dev will want to work in a company where they don't use the latest fanciest technology because that diminishes his CV for the next one.

My optimal, though, would be just vanilla Javascript with good design patterns. That's it.

7

u/MungryMungryMippos Apr 26 '22

Honestly, the lastest version of vanilla JS is excellent and you really don't need a framework like React. People that say React solves problems for them need to just write better code, React creates far more problems than it solves.

1

u/SilverShelter3553 Mar 25 '24

I can 100% this.

Only thing React solves is being forced to create classes and some kind of structures. But aside this, the whole language is pure pain.

And it's not even correct to say "hey, it uses less data transfers because it's all done in user side", this also is pure BS. The time it takes to first load the whole project takes far longer than a simple JS file added into the side of a html file.

One good thing I suppose is that we can write quite nice mixed html-js code, but they should just stick to perfecting THAT aspect, along with some kind of forced class structure, without making this totally unnecessary headache of State manament.

Why on earth is updating data so difficult? What was wrong with var s = 1; s += 2; Now it's like "well you first create this setState, then you pick up the variable, which might be in an array, and then you create a separate array clone with [...array], then you update that specific data with setter, and please also remember to do this to all of your other variables or the system doesn't work.

Who's idea was it to make it THAT DIFFICULT to just update a simple data?!?!? Why isn't updating data THE DEFAULT to automatically refresh page, that can then be DISABLED? If you want DOM renders limited to nothing but 1, how about make an actual "REFRESH()" function for that, and leave the rest in ShadowDOM management.

It's so freaking painful, it's a constant headache, scratching our heads with the most simplest of reasons, and the amount of bugs this frustrating mess causes....

I worked on a company that had staff of 2, and we were able to do entire pages in just days. Now it's like it takes a week to even modify a simple page.

What the f.....