It's based as long as you don't do something boring with it. Try to stand out from other websites instead of just making it looking like another typical flat design wix site.
>show a modal dialog
Are you retarded? Use 'createPortal' from react-dom you fucking moron.
https://react.dev/reference/react-dom/createPortal
React is amazing, but people like this retard are the reason why people think it's shit. I've worked on 3 different apps using react, and all of them had the same issues where 'senior' devs think they're too good to read the fucking react documentation and the app is a shitshow as a result. The number one mistake I see people making is not putting things that affect the render in state, and then they bitch and moan that the app isn't updating. It's like they do not understand the core principals of react and do not care to use them. And if you do not follow the basic rules of react then you may as well not use it. I also commonly see people fuck-up react's effect principles, e.g. declaring functions outside of a 'useEffect' block then not adding it as a dependency and wondering why it's internal state is stale, async functions in useEffect blocks that end with a setState and do not have an abort/cancel mechanism, etc.
Why the fuck should I define all my helper functions, parsers, and other methods inside a use effect?
What if I have two use effects that use the same helper method? You want me to define them twice??
>is allocating an entirely new array and copying your existing array over every time you add an element to the end based?
This is a retarded take. Do you think it's more expensive to iterate over that array and perform some deep equality check on every element EVERY SINGLE TIME your application needs to determine whether or not the component should rerender? Obviously this would be garbage performance wise, it is much more efficient to just see if the new array references the old array in memory, and rerender based off of that simple equality check.
Sure, it would be more performant to use mutable state design, and manually tell the app when you update state and want to rerender. YOU CAN FUCKING DO THIS IN REACT YOU RETARD. It is officially supported now with 'useSyncExternalStore'. Make your own fucking store that follows all of the state-management principles you desire.
>React is based, you just have to remember to wrap everything in 10 different variations of useWorkaround and define the dependencies manually because why would the framework do that
Everything being a function that has to re-run on every single state change is fundamentally flawed design. In other frameworks you don't have to worry about shit like stale closures.
>is allocating an entirely new array and copying your existing array over every time you add an element to the end based?
This is a retarded take. Do you think it's more expensive to iterate over that array and perform some deep equality check on every element EVERY SINGLE TIME your application needs to determine whether or not the component should rerender? Obviously this would be garbage performance wise, it is much more efficient to just see if the new array references the old array in memory, and rerender based off of that simple equality check.
Sure, it would be more performant to use mutable state design, and manually tell the app when you update state and want to rerender. YOU CAN FUCKING DO THIS IN REACT YOU RETARD. It is officially supported now with 'useSyncExternalStore'. Make your own fucking store that follows all of the state-management principles you desire.
>Anything that breaks the moment a user disables javascript is far from based.
Oh so every fucking interactive website is 'far from based'? What the fuck are you talking about? Of course applications do not work with JS disabled. If you're using React to fucking build some website that doesnt need to function as an application you're already retarded. Only use case where that makes sense is if your site a blog and are using something like NextJS to generate pages, and in that scenario NextJS already bundles up a static html site.
You make no sense and should be on meds. Website applications and interactivity were a thing before javascript was even invented.
React devs are just too stupid to learn a little AJAX which is the appropriate choice if eliminating the page refresh is really that important.
React is the reason websites run like shit and take forever to load. It adds way more complexity than it removes and makes deployment more cumbersome than it needs to be. Total garbage heap of a framework, but unfortunately worth learning since it may get you a job.
t. rewrote my react project in vanilla js
no, it's shitty, i deal with it daily and hate it, wish i could just deal with terraform, linux and scripting all day, hell would rather program in ASM than use pajeetscript
It's based as long as you don't do something boring with it. Try to stand out from other websites instead of just making it looking like another typical flat design wix site.
based until you need to draw a data grid or show a modal dialog
>show a modal dialog
Are you retarded? Use 'createPortal' from react-dom you fucking moron.
https://react.dev/reference/react-dom/createPortal
React is amazing, but people like this retard are the reason why people think it's shit. I've worked on 3 different apps using react, and all of them had the same issues where 'senior' devs think they're too good to read the fucking react documentation and the app is a shitshow as a result. The number one mistake I see people making is not putting things that affect the render in state, and then they bitch and moan that the app isn't updating. It's like they do not understand the core principals of react and do not care to use them. And if you do not follow the basic rules of react then you may as well not use it. I also commonly see people fuck-up react's effect principles, e.g. declaring functions outside of a 'useEffect' block then not adding it as a dependency and wondering why it's internal state is stale, async functions in useEffect blocks that end with a setState and do not have an abort/cancel mechanism, etc.
Why the fuck should I define all my helper functions, parsers, and other methods inside a use effect?
What if I have two use effects that use the same helper method? You want me to define them twice??
browsers already have dialog/modal implementation with dialog tag, why is react over-engineering stuff?
>React is based, you just have to remember to wrap everything in 10 different variations of useWorkaround and define the dependencies manually because why would the framework do that
Everything being a function that has to re-run on every single state change is fundamentally flawed design. In other frameworks you don't have to worry about shit like stale closures.
Modals are just shit all around, bad UX and a pain in the ass to make work properly in any framework.
Literally just don't use them.
It's bloated pajeet shit. Your website doesn't need it.
is allocating an entirely new array and copying your existing array over every time you add an element to the end based?
>is allocating an entirely new array and copying your existing array over every time you add an element to the end based?
This is a retarded take. Do you think it's more expensive to iterate over that array and perform some deep equality check on every element EVERY SINGLE TIME your application needs to determine whether or not the component should rerender? Obviously this would be garbage performance wise, it is much more efficient to just see if the new array references the old array in memory, and rerender based off of that simple equality check.
Sure, it would be more performant to use mutable state design, and manually tell the app when you update state and want to rerender. YOU CAN FUCKING DO THIS IN REACT YOU RETARD. It is officially supported now with 'useSyncExternalStore'. Make your own fucking store that follows all of the state-management principles you desire.
or just do ssr with a real language...
>or just do ssr with a real language...
Hahahahaha, you people have no fucking clue what you are talking about.
I still don't get what's the point of react other than for paying your bills and loans?
Anything that breaks the moment a user disables javascript is far from based.
>Anything that breaks the moment a user disables javascript is far from based.
Oh so every fucking interactive website is 'far from based'? What the fuck are you talking about? Of course applications do not work with JS disabled. If you're using React to fucking build some website that doesnt need to function as an application you're already retarded. Only use case where that makes sense is if your site a blog and are using something like NextJS to generate pages, and in that scenario NextJS already bundles up a static html site.
You make no sense and should be on meds. Website applications and interactivity were a thing before javascript was even invented.
React devs are just too stupid to learn a little AJAX which is the appropriate choice if eliminating the page refresh is really that important.
React is the reason websites run like shit and take forever to load. It adds way more complexity than it removes and makes deployment more cumbersome than it needs to be. Total garbage heap of a framework, but unfortunately worth learning since it may get you a job.
t. rewrote my react project in vanilla js
no, it's shitty, i deal with it daily and hate it, wish i could just deal with terraform, linux and scripting all day, hell would rather program in ASM than use pajeetscript
JSX is so positively monstrously ugly that i can't even begin to comprehend the utmost horrendous hideousness of it