30

I hate React.js with a fucking passion. It sounds great on paper, but once your project gets any size. The mental recursive loops of passing data around is insane. Not to mention keeping consistency a cross metric shit ton of components. How do you manage it?

Comments
  • 15
    To add any functionality I have to do changes in at least 8 files and components consistently need to be rewritten. It is such a pain to write trivial shit over and over, because it is the React way. I am so triggered.
  • 9
    I agree, the flow of data is confusing.
  • 3
    @Letmecode Yeah, I got Redux, but there are too many components that have way too many states and child components. Too many edge cases. Always passing props.
  • 0
    @Letmecode i think what he means is that how we are told that dividing components into many sub components is good. This results in passing the state of the parent as a prop to the children, which is then passed into its state, and subsequently its children. Redux is very good in this regard.
  • 10
    and the day you master it, a new out of the box, fresh and hip library will be released and this rant will repeat itself 😂😂😂,
  • 0
    check out redux!
  • 3
    Thanks for the heads up, sticking to express and sails
  • 6
    React is to be used in projects that need it. Otherwise it is Hype Driven Development :)
  • 0
    Try aurelia.js
    It tries to stick to ES6 without complilcating it too much.
    Its component and value bimding systems are good.
    Check it out-> aurelia.io
  • 1
    Any feature rich app becomes complex. Does not matter if you use vanilla js or a framework.

    Btw if you need 8 new files for a new functionality, maybe you should revisit your approach.
  • 0
    @AlexDeLarge sounds like he did and the problem is there actually. React unfortunately gets a lot of bad rep because of redux. Immutable and mobx are nice though, still waiting for a middle ground.
  • 7
    I do Angular, JQuery, Ajax, JavaScript, Razor, Node, Express and now I'm starting to learn React. Have to say that I am finding it a hot mess to jump into. All this state management crap with Redux and MobX the main problem. We've been maintaining state in every language since COBOL some thirty years ago. Not a problem. Can't find a single React-TypeScript-MobX tutorial or github that is not broken due to library changes. So why would i spend money on a book that probably has code that doesn't work anymore? Its a hot mess. Glad there is Angular.
  • 9
    Repeat after me :
    I will not write HTML within JavaScript
    I will not write HTML within JavaScript
    I will not write HTML within JavaScript

    (and I know it's JSX, don't get me wrong, the idea is still shit to me). Angular's separation of concerns is way better to me.
  • 10
    React is for lazy and/or bad programmers. It is popular because most programmers are bad and/or lazy! That is perhaps harsh, but it is also true.

    A framework solves nothing, it is just a simplified wrapper which restricts functionality of lower level code — in this case Javascript, CSS, HTML.

    Bootstrap, Angular, React and even jQuery ... are all dire because the restrictions they impose result in more complexity in trying to break those restriction, even in simple ways.

    An exception is Three.js which is a wrapper for the 3D context of canvas. 3D programming is so complex in WebGL that a high-level wrapper for basic routines allows functionality for people who aren't wizards in 3D mathematics.

    But the above proves my initial point — "a person incapable of WebGL would use Three.js."

    However, javascript is not hyper-complex, it is not 3D maths, the contrary, it is the basic language we should be coding.

    A developer who uses React is one step away from a Wordpress blogger.
  • 0
    @mclayoz Thank you for saying it
  • 1
    I hate React with more passion than you
  • 3
    I was thinking of learning React because I keep seeing it pop up everywhere, but I met a react fanboy douche interviewer. I took a bloodoath to never learn that shit.
  • 0
    I see some recommendations to try redux. Redux and Abramov are fucking terrible.
  • 1
    React is the epitome of what's wrong with all front-end development these days, a tornado of libraries, driven by hype, and every-time you complain about anything, some asshole will just recommend another library for you.
  • 1
    @crazybaboon Hey man, don't compare the steaming pile of React framework to Three.js.

    For those fanbois who keep repeating "React is library not a framework": Library is something your code calls. Framework is something that calls your code. React is definitely a framework.

    Libraries are fine. Even jQuery, being a library we can easily take it out and swap it for fast, clean, vanilla js. But if you have an app written for React framework, it's a re-write to convert to be vanilla.
  • 2
    React by no means is the most Garbage shit I have ever came across period! I am actually an Android Developer, I am quite fluent with Angular as well. Because of my work, I had to work with two react js projects. And gotta say man, its fucking Garbage! The code looks like pile of shit! So called JSX "Actually it is fucking html lol" wrapped around with javascript I mean seriously? I do not use Angular unless I have plan to create my own apps, but, Angular is far far better than this dumb as react js! Stay away from this shit man! Happy coding :)
  • 2
    Finally, other people who also hates Reactjs! So many people talking about how great it is and when I tried it out I thought they had all been pranking me ... still, after giving it more time and work, my opinion hasn't changed, just got more confirmed that it is the messiest _blank_ ever...
  • 0
  • 0
    @juniayulia speak it brother, speak
  • 2
    I'm sick of React. As a web dev, I don't like HTML in JS. Started using Svelte sometime ago and I can say there is still hope.
  • 1
    HTML is NOT meant to be written in Javascript. It's exactly the other way around. I FUCKING HATE REACT, WITH A PASSION!
Add Comment