5:34: _I hated it at first, but now I cannot live without it._ Sounds like a very bad drug then, or a destructive cult. I recommend AA or consulting some deprogrammers.
@@DnBComplex do you expect me to write entire article here? Historical aspects require a lot of context, you know. Not very comments-like content. React is yet another dependency, that bears weight before even you start to make your app. Then we’ve come across the whole cycle, from php and server rendering, to client rendering, to server rendering again, and now we’re at isomorphic rendering. Did you ever heard the joke how we’ve finally back to server rendering, a feature that was present in php in 1995 and now finally React is catching up? Unfortunately not everybody comes across all those cycles, and many still stuck at making those dumb SPAs. If it’s not SPAa they building, their server only prerenders menus etc statics, while dynamic content is loaded by browser, which is isn’t ideal either. And that is why it is so often compared «how websites in the past are so much more faster and a better product». Some dumb php sites beat this react ten times in those aspects. In React, it is too easy to write shitty code, and that is why there’s so many shitty apps made with React. Also React is a whole 100kb to the page, 200kb with react-dom, well 25-100kb after optimizations, that’s still some load you have to take before you even start making your app logic. Single TCP pckage contains 14kb worth of data. And with react, you already guarantee that you will be having multiple roundups, though you haven’t even put your actual app in the packets yet. Then add some libraries (js-packages), plus your app code, plus some i18n built into client sometimes, plus ads, that is why so many websites is a bloatware having to download megabytes for the initial request. Not to mention there are much shorter ways to write components, like Vue or Svelte. Some smart people even call react not truly reactive (because reactive is a certain pattern and it is made better in non-react frameworks like Vue or Svelte). Currently, the most technically advanced way to develop a web app - is to put as much as possible into compile time, freeing both the server and client from the work, which is especially important for client, and allowing the client to save on app size. Svelte is doing great at all this, and the code not just shorter, but better. Vue probably also good enough also but I personally chosen Svelte. Although it is technically possible to write bad code in Svelte, it is much more suitable to write good code, than React, because it is isomorphic by default - and also it is with less bundle size, less code to maintain, fewer tab spaces, most things at compile time as I said, their bundler is also faster than webpack, etc etc etc. React should be hated, just like PHP started to gain hate when React came. PHP is still more than 50% Internet, so react won’t disappear in a day either - thus, the hate. They were important step in technology, it’s only too bad so many people can’t step over it.
@@DnBComplex do you expect me to write entire article here? Historical aspects require a lot of context, you know. Not very comments-like content. React is yet another dependency, that bears weight before even you start to make your app. Then we’ve come across the whole cycle, from php and server rendering, to client rendering, to server rendering again, and now we’re at isomorphic rendering. Did you ever heard the joke how we’ve finally back to server rendering, a feature that was present in php in 1995 and now finally React is catching up? Unfortunately not everybody comes across all those cycles, and many still stuck at making those dumb SPAs. If it’s not SPAa they building, their server only prerenders menus etc statics, while dynamic content is loaded by browser, which is isn’t ideal either. And that is why it is so often compared «how websites in the past are so much more faster and a better product». Some dumb php sites beat this react ten times in those aspects. In React, it is too easy to write sh*tty code, and that is why there’s so many slow apps made with React. Also React is a whole 100kb to the page, 200kb if with react-dom, although it’s 25-100kb after optimizations, that’s still some load you have to take before you even start making your app logic. Single TCP pckage contains 14kb worth of data. And with react, you already guarantee that you will be having multiple roundups, though you haven’t even put your actual app in the packets yet. Then add some libraries (js-packages), plus your app code, plus some i18n built into client sometimes, plus ads, that is why so many websites is a bloatware having to download megabytes for the initial request. Not to mention there are much shorter ways to write components, like Vue or Svelte. Some smart people even call react not truly reactive (because reactive is a certain pattern and it is made better in non-react frameworks like Vue or Svelte). Currently, the most technically advanced way to develop a web app - is to put as much as possible into compile time, freeing both the server and client from the work, which is especially important for client, and allowing the client to save on app size. Svelte is doing great at all this, and the code not just shorter, but better. Vue probably also good enough also but I personally chosen Svelte. Although it is technically possible to write bad code in Svelte, it is much more suitable to write good code, than React, because it is isomorphic by default - and also it is with less bundle size, less code to maintain, fewer tab spaces, most things at compile time as I said, their bundler is also faster than webpack, etc etc etc. React should be hated, just like PHP started to gain hate when React came. PHP is still more than 50% Internet, so react won’t disappear in a day either - thus, the hate. They were important step in technology, it’s only too bad so many people can’t step over it.
I still hate react to this day. Even though I learned React, I didn't had a chance to get a work where I can apply React. Even for personnal project, I hate to apply it.
@@seanballais Pretty simply really. At its origin in 2010ish, React perpetuated all the patterns of the day that were recognised as bad because they produced bad code while its competitors have moved on and adopted modern patterns. Examples being mixing up html with css and javascript. Only the react fan brigade believe that is a good practice. Then you have the issue of plugins. React requires at least a dozen plugins before you can do anything useful with it. We had that in 2010 with JQuery 'plugin hell'. Then you have got the 'library' vs 'framework' issue. Because it is a library, it is designed to be added to other things. That means there are no standard patterns, every developer does it their own way and no two React apps are structured in the same way. Then there is boilerplate code and no dependency injection. In every React environment I have worked in, I have seen developers fiddling around wasting huge amounts of time writing trivial, unnecessary boilerplate code (mostly stuff fiddling with DOM and css) that should already exist and be encapsulated like it is in Angular. Oh, and let's not forget that horrible feature of features: I've forgotten what they call it, but it involves a mechanism that passes parameters down a component stack. I can't honestly think of a worst form of coupling! And the general structure of a React App: the whole thing is about chaining function calls. There's nothing object oriented about that, especially when classes seem to be discouraged! And unfortunately, this is a bad pattern that seems to be infiltrating other languages now. At the end of the day, you have to remember that React was designed by UI developers (who are mostly, not qualified professional software engineers - they are graphics people) for UI developers. That's why it doesn't follow most good engineering practice and requires heaps of plugins to 'fudge' it to make it appear that it is playing lip-service to modern patterns.
@@aigabuskira165 every time I have to work with it, it just reminds me of the bad old days around 2010 when we used to have lots of patterns that produced badly structured code. React seems to perpetuate all of the bad practices of 2010 while its competitors went on to adopt all the modern good practice patterns 'out of the box' - like Angular.
Never seen something that's as overrated as React. We now have developers who believe you can't build anything without React. And it's gonna get worse because every AI tool out there thats being used to build the next Facebook seems to prefer React/NextJS
React certainly has its place in the front-end world, but it should be used in projects that fit into it. In the hands of technically experienced professionals, React is a powerful tool for creating reliable, efficient, scalable digital products. To sum it up from a developer’s perspective, I wouldn’t say that React is better or worse than any other popular JavaScript framework. The important thing is to match the tool to the problem, not the other way around. On the other hand, if one were to look at it from a business perspective, I would say that React dominates the market. Mainly because of the large number of developers, many packages are created for many business cases, and applications are developed by the largest community, which makes development easier and faster.
I was at the JSConf EU of 2013 when Pete Hunt was introducing React. It immediately clicked with me, and I had that silver bullet feeling. But I totally remember all the skeptical voices.
@@CodeSource Absolutely! I was even lucky enough to visit the JSConf EU 2009 already when Ryan Dahl introduced Node.js. There was no protest at all but standing ovations! Regarding React: Something not many people know is that it was originally prototyped in SML, and then OCaml, and later ported to JS. That's also where the idea of JSX came from. I'm a bit sad that ReasonML/ReScript, which is based on OCaml, didn't take off. It had so much potential and was better compared to TypeScript in many ways. Probably it was too different from JS to be widely adopted.
React is for building web applications, however your animations only contain mobile apps which is kinda misleading. Those would be great for a story of react native. Great video still.
There is no need to discuss about it. The syntax says how awful React is. This is the most simplest example on earth. Now imagine a big project. React: const [value, setValue] = useState(0) increase = () => { setValue(lastValue => lastValue + 1); } Angular: value = 0; increase() { value++; }
@@vladyslavdidukh8833 The useState "hook" creates a mutable variable somewhere in memory that you don't directly access. It returns a pair of (readonly that is the current value of that variable) and (function which updates that inaccessible mutable variable and triggers stuff to happen too). Heard in 3:14 how in React you throw out everything and rerender everything? The moment you call setValue this whole component is destroyed together with those two constants. And it gets remade from scratch with a new const, this time initialized by whatever the inaccessible mutable variable was set to.
React is horrible and must be banned by governments. The complexity of tyrant react js is unacceptable. Why coders are making their lives much harder by licking react js? Mature humans choose simplicity , but f react js is the opposite.
9:38 clean architecture? like everything is nested... Modern Angular have most understandable architecture in my opinion - easy to see what is going on even in bigger project.
React is the worst nigthmare i had, i had the worst time in my coding career when i wrote react projects. Jquery and vanilla js is way better in these days. I even prefer to write assembly rather than react, at least i don't deal with mounting and hydration bullshits.
How do you compare Angular JS to modern Angular? I'm learning the modern version because of job reasons. Not that I love it. 👉There is almost no Java developer position in Switzerland without Angular requirement!
and so is svelte, so is vue, so is solid, and so on.. react is just.. it's been there for long enough. kind of like people still using bootstrap and jquery in 2025 the point isnt that it's old and noone should use it anymore, more like that's it's become some sort of standard that simply, works, does the job so why wouldn't people use it :) but yeh, now that my company has finally switched to sveltekit, i wouldn't ever go back to react.
Good video. Very interesting to see the criticism of React in the comments. I wonder if this is reflecting of the "wider community" or just so happens to be the people who have seen this video. Personally though I think these comments make sense. React is quite complex and it does seem that other frameworks are simpler with modern versions.
React is bad, really really bad. It is the Abyss of tech rages, where fanboy hordes praise a sane stateful development model, MVC, on web, which is a stateless technology. In order to fix this mismatch, it peruses every operating systems nightmare language JavaScript, which is a LISP with a pseudo-seagull syntax without compilation or type control! (WASM has no connection to GUI, so gotcha!) All modern garbs systems follow the philosophy that: _start to garb when memory is running out._ This is wrong and insane, since all programs start to garb at the same time, as well as the OS starting to swap memory, the philosophy should have been: _dedicate a background process that garbs ASAP._ Everything about implementing GUI on web is a dead end. When states start to enforce stable systems development, all React and all Electron applications will get into the view of the grim reaper. Don't waste your time on this nonsense!
Well, React and React Native broke pretty much everything on Web and Mobile apps 😅 . What good is a single codebase when the resulting app underperforms, to the point of actively hindering its usage, in pretty much every single platform it's exported to?
That's why i only write websites with HTML 3.2 with JPEGs that are under 50K, just like the 1990s intended. BOOM! Page loads!! ooh yea, and use clicky keyboards with ball mice and CRTs 🤣🤣
Back in the 2000's we had classic ASP which mixed up html and javascript with the help of JQuery - this is basically what JSX is. We cursed it as bad due to no separation between UI definition (html) and code. We got given Webforms which did separate them. That lasted until we wanted to do proper MVC. React just regurgitates all the bad practices of old. It should be banned because it is going to create a massive tech-debt problem very soon.
Biggest fail that fb make is react, most people left platform because of slowness, but fb came all the ways possible like in the phones, etc that they continue expanding. But react get it self mostly fixed with hooks
@ any technology that has stayed for this long with a wide adoption simply buttresses React’s argument. React is not perfect but gets the job done. Just came out of an interview and guess what it was all about? React!
I am still thinking whether I should just learn JavaScript ONLY. I have many books and udemy course bought past 3 months, but still have the inertia to even look at the first pages. You see, I had to close my medical GP clinic few months ago and thinking that I could deal with Web programming which I hated. since late 1990s. My hobby thrill is just Linux and DBASE 2. Not knowing human race has just created a complexity, React. Have to learn Web for freelancing.
Overwhelmed with tech management? Connect with us today for tailored software services: CodeSource.io/projects
5:34: _I hated it at first, but now I cannot live without it._ Sounds like a very bad drug then, or a destructive cult. I recommend AA or consulting some deprogrammers.
Sounds like a line from 1984 :D
Well i'm looking for a better drug at this point
You're 3-4 years late. The modern view changed from skepticism to approval, to hate. You're stuck at views of 2016-2022
Can you please elaborate more on this? I am interested in historical aspects of programming.
Uhh no its not. JS sucks, but react is great. Especially with TS
@@DnBComplex do you expect me to write entire article here? Historical aspects require a lot of context, you know. Not very comments-like content. React is yet another dependency, that bears weight before even you start to make your app. Then we’ve come across the whole cycle, from php and server rendering, to client rendering, to server rendering again, and now we’re at isomorphic rendering. Did you ever heard the joke how we’ve finally back to server rendering, a feature that was present in php in 1995 and now finally React is catching up? Unfortunately not everybody comes across all those cycles, and many still stuck at making those dumb SPAs. If it’s not SPAa they building, their server only prerenders menus etc statics, while dynamic content is loaded by browser, which is isn’t ideal either. And that is why it is so often compared «how websites in the past are so much more faster and a better product». Some dumb php sites beat this react ten times in those aspects. In React, it is too easy to write shitty code, and that is why there’s so many shitty apps made with React. Also React is a whole 100kb to the page, 200kb with react-dom, well 25-100kb after optimizations, that’s still some load you have to take before you even start making your app logic. Single TCP pckage contains 14kb worth of data. And with react, you already guarantee that you will be having multiple roundups, though you haven’t even put your actual app in the packets yet. Then add some libraries (js-packages), plus your app code, plus some i18n built into client sometimes, plus ads, that is why so many websites is a bloatware having to download megabytes for the initial request. Not to mention there are much shorter ways to write components, like Vue or Svelte. Some smart people even call react not truly reactive (because reactive is a certain pattern and it is made better in non-react frameworks like Vue or Svelte). Currently, the most technically advanced way to develop a web app - is to put as much as possible into compile time, freeing both the server and client from the work, which is especially important for client, and allowing the client to save on app size. Svelte is doing great at all this, and the code not just shorter, but better. Vue probably also good enough also but I personally chosen Svelte. Although it is technically possible to write bad code in Svelte, it is much more suitable to write good code, than React, because it is isomorphic by default - and also it is with less bundle size, less code to maintain, fewer tab spaces, most things at compile time as I said, their bundler is also faster than webpack, etc etc etc. React should be hated, just like PHP started to gain hate when React came. PHP is still more than 50% Internet, so react won’t disappear in a day either - thus, the hate. They were important step in technology, it’s only too bad so many people can’t step over it.
@@DnBComplex do you expect me to write entire article here? Historical aspects require a lot of context, you know. Not very comments-like content. React is yet another dependency, that bears weight before even you start to make your app. Then we’ve come across the whole cycle, from php and server rendering, to client rendering, to server rendering again, and now we’re at isomorphic rendering. Did you ever heard the joke how we’ve finally back to server rendering, a feature that was present in php in 1995 and now finally React is catching up? Unfortunately not everybody comes across all those cycles, and many still stuck at making those dumb SPAs. If it’s not SPAa they building, their server only prerenders menus etc statics, while dynamic content is loaded by browser, which is isn’t ideal either. And that is why it is so often compared «how websites in the past are so much more faster and a better product». Some dumb php sites beat this react ten times in those aspects. In React, it is too easy to write sh*tty code, and that is why there’s so many slow apps made with React. Also React is a whole 100kb to the page, 200kb if with react-dom, although it’s 25-100kb after optimizations, that’s still some load you have to take before you even start making your app logic. Single TCP pckage contains 14kb worth of data. And with react, you already guarantee that you will be having multiple roundups, though you haven’t even put your actual app in the packets yet. Then add some libraries (js-packages), plus your app code, plus some i18n built into client sometimes, plus ads, that is why so many websites is a bloatware having to download megabytes for the initial request. Not to mention there are much shorter ways to write components, like Vue or Svelte. Some smart people even call react not truly reactive (because reactive is a certain pattern and it is made better in non-react frameworks like Vue or Svelte). Currently, the most technically advanced way to develop a web app - is to put as much as possible into compile time, freeing both the server and client from the work, which is especially important for client, and allowing the client to save on app size. Svelte is doing great at all this, and the code not just shorter, but better. Vue probably also good enough also but I personally chosen Svelte. Although it is technically possible to write bad code in Svelte, it is much more suitable to write good code, than React, because it is isomorphic by default - and also it is with less bundle size, less code to maintain, fewer tab spaces, most things at compile time as I said, their bundler is also faster than webpack, etc etc etc. React should be hated, just like PHP started to gain hate when React came. PHP is still more than 50% Internet, so react won’t disappear in a day either - thus, the hate. They were important step in technology, it’s only too bad so many people can’t step over it.
@@BigBrotha3459 react sucks
The next video: "The Untold Story of Vue" plz, I love this video
I still hate react to this day. Even though I learned React, I didn't had a chance to get a work where I can apply React. Even for personnal project, I hate to apply it.
Same here. I hate React. It encourages the production of piles of crap code using every method that we fought against to get rid of back in 2010!
i get the chance to get a work with it, still i hate it even more.
@@gppsoftware Do tell more!
@@seanballais Pretty simply really. At its origin in 2010ish, React perpetuated all the patterns of the day that were recognised as bad because they produced bad code while its competitors have moved on and adopted modern patterns. Examples being mixing up html with css and javascript. Only the react fan brigade believe that is a good practice. Then you have the issue of plugins. React requires at least a dozen plugins before you can do anything useful with it. We had that in 2010 with JQuery 'plugin hell'. Then you have got the 'library' vs 'framework' issue. Because it is a library, it is designed to be added to other things. That means there are no standard patterns, every developer does it their own way and no two React apps are structured in the same way. Then there is boilerplate code and no dependency injection. In every React environment I have worked in, I have seen developers fiddling around wasting huge amounts of time writing trivial, unnecessary boilerplate code (mostly stuff fiddling with DOM and css) that should already exist and be encapsulated like it is in Angular. Oh, and let's not forget that horrible feature of features: I've forgotten what they call it, but it involves a mechanism that passes parameters down a component stack. I can't honestly think of a worst form of coupling! And the general structure of a React App: the whole thing is about chaining function calls. There's nothing object oriented about that, especially when classes seem to be discouraged! And unfortunately, this is a bad pattern that seems to be infiltrating other languages now.
At the end of the day, you have to remember that React was designed by UI developers (who are mostly, not qualified professional software engineers - they are graphics people) for UI developers. That's why it doesn't follow most good engineering practice and requires heaps of plugins to 'fudge' it to make it appear that it is playing lip-service to modern patterns.
@@aigabuskira165 every time I have to work with it, it just reminds me of the bad old days around 2010 when we used to have lots of patterns that produced badly structured code. React seems to perpetuate all of the bad practices of 2010 while its competitors went on to adopt all the modern good practice patterns 'out of the box' - like Angular.
Never seen something that's as overrated as React. We now have developers who believe you can't build anything without React. And it's gonna get worse because every AI tool out there thats being used to build the next Facebook seems to prefer React/NextJS
yeah react is bad
😂😂
And they were correct to mock it!
I still don't see why devs just won't use ELM. I mostly use go and elm
React certainly has its place in the front-end world, but it should be used in projects that fit into it. In the hands of technically experienced professionals, React is a powerful tool for creating reliable, efficient, scalable digital products.
To sum it up from a developer’s perspective, I wouldn’t say that React is better or worse than any other popular JavaScript framework. The important thing is to match the tool to the problem, not the other way around.
On the other hand, if one were to look at it from a business perspective, I would say that React dominates the market. Mainly because of the large number of developers, many packages are created for many business cases, and applications are developed by the largest community, which makes development easier and faster.
I was at the JSConf EU of 2013 when Pete Hunt was introducing React. It immediately clicked with me, and I had that silver bullet feeling. But I totally remember all the skeptical voices.
That's awesome! Being there at the beginning of something big must have been exciting, even with the skepticism😅
@@CodeSource Absolutely! I was even lucky enough to visit the JSConf EU 2009 already when Ryan Dahl introduced Node.js. There was no protest at all but standing ovations!
Regarding React: Something not many people know is that it was originally prototyped in SML, and then OCaml, and later ported to JS. That's also where the idea of JSX came from. I'm a bit sad that ReasonML/ReScript, which is based on OCaml, didn't take off. It had so much potential and was better compared to TypeScript in many ways. Probably it was too different from JS to be widely adopted.
React is for building web applications, however your animations only contain mobile apps which is kinda misleading. Those would be great for a story of react native. Great video still.
There is no need to discuss about it. The syntax says how awful React is.
This is the most simplest example on earth. Now imagine a big project.
React:
const [value, setValue] = useState(0)
increase = () => {
setValue(lastValue => lastValue + 1);
}
Angular:
value = 0;
increase() {
value++;
}
How have you incremented constant value?
@@vladyslavdidukh8833 I fixed it. Thanks for checking my pull request 🙂
It's not incrementing a constant. It's just how React works internally
@@vladyslavdidukh8833
The useState "hook" creates a mutable variable somewhere in memory that you don't directly access.
It returns a pair of (readonly that is the current value of that variable) and (function which updates that inaccessible mutable variable and triggers stuff to happen too).
Heard in 3:14 how in React you throw out everything and rerender everything?
The moment you call setValue this whole component is destroyed together with those two constants.
And it gets remade from scratch with a new const, this time initialized by whatever the inaccessible mutable variable was set to.
You forgot useeffect, the mother of bugs
All thanks to Zucc
React is still bad.
React is horrible and must be banned by governments. The complexity of tyrant react js is unacceptable. Why coders are making their lives much harder by licking react js? Mature humans choose simplicity , but f react js is the opposite.
Skill issue
Yeah, we should all use Vue
What do you suggest we use then
@jayjorneypua8174 Angular, Svelte
@@jayjorneypua8174 the one that pays 😁
React for the haters...
Never learned it, never will.
9:38 clean architecture? like everything is nested...
Modern Angular have most understandable architecture in my opinion - easy to see what is going on even in bigger project.
React is the worst nigthmare i had, i had the worst time in my coding career when i wrote react projects. Jquery and vanilla js is way better in these days. I even prefer to write assembly rather than react, at least i don't deal with mounting and hydration bullshits.
Angular developer: "We'll see about that 😉"
there is a lot of technology stories, go on
Glad that i learned react after working in angular for 3 years, i choose react anyday.
Please create about Flutter
I hate React after 1 year working with. Angular much better to write and maintain
I still perfer Angular Js which is 10 times more easy to develop in it. Also Htmx is much more simple than react
How do you compare Angular JS to modern Angular?
I'm learning the modern version because of job reasons. Not that I love it.
👉There is almost no Java developer position in Switzerland without Angular requirement!
@@javastream5015 oof Java + Angular....double whammy masochism!
and so is svelte, so is vue, so is solid, and so on.. react is just.. it's been there for long enough. kind of like people still using bootstrap and jquery in 2025 the point isnt that it's old and noone should use it anymore, more like that's it's become some sort of standard that simply, works, does the job so why wouldn't people use it :) but yeh, now that my company has finally switched to sveltekit, i wouldn't ever go back to react.
@ Me neither, React had a run... wouldn't call it a good one. It was just there to replace jQuery.
And Vue is even better
Good video.
Very interesting to see the criticism of React in the comments. I wonder if this is reflecting of the "wider community" or just so happens to be the people who have seen this video.
Personally though I think these comments make sense. React is quite complex and it does seem that other frameworks are simpler with modern versions.
You are confusing between angularjs and angular
And most frameworks have components
I love React. It is simple and powerful.
And more jobs.
React syntax and way of doing things is still shit. VUE is much better. I only HAVE TO USE React bcz of its wayyyyyyyyy larger ecosystem
I loved Vue2 with options api over React, but now Vue3 with composition api feels like react, but worse 😅
I still hate it 😂
SolidJS or Svelte is so much better than React in 2025
solid is a copycat of react, but indeed svelte is.
@@haliszekeriyaozkok4851 SolidJS runs faster than React, and easier to code
@@haliszekeriyaozkok4851its the opposite actually, react is stealing solid's idea, and somehow able to make it worse
So what should we learn instead of React 😢
All Data Binding concepts came from the foundations laid by Microsoft's in WPF and their other tech.
Informative video
I used to build web app with backbonejs
video is good. visuals, animations, voice and explanation is good
Same thing is supported by angular without wierd syntax,
With build in ssr, standalone components, and introduction of signal made it more powerful.
React is bad, really really bad. It is the Abyss of tech rages, where fanboy hordes praise a sane stateful development model, MVC, on web, which is a stateless technology. In order to fix this mismatch, it peruses every operating systems nightmare language JavaScript, which is a LISP with a pseudo-seagull syntax without compilation or type control! (WASM has no connection to GUI, so gotcha!) All modern garbs systems follow the philosophy that: _start to garb when memory is running out._ This is wrong and insane, since all programs start to garb at the same time, as well as the OS starting to swap memory, the philosophy should have been: _dedicate a background process that garbs ASAP._ Everything about implementing GUI on web is a dead end. When states start to enforce stable systems development, all React and all Electron applications will get into the view of the grim reaper. Don't waste your time on this nonsense!
Lmao sure
Well described ❤️
"If it isn't broken, don't touch it"
And that's 101 on "How To Avoid Problems And Growth"
But everything IS broken. And it still is.
Well, React and React Native broke pretty much everything on Web and Mobile apps 😅 .
What good is a single codebase when the resulting app underperforms, to the point of actively hindering its usage, in pretty much every single platform it's exported to?
i built a fortune witn react. i simply cant hate it😂😂😂
That's why i only write websites with HTML 3.2 with JPEGs that are under 50K, just like the 1990s intended.
BOOM! Page loads!! ooh yea, and use clicky keyboards with ball mice and CRTs 🤣🤣
now it feels like all frameworks should do the jsx instead of creating new syntax and just then implement their framework feature on top off it
Back in the 2000's we had classic ASP which mixed up html and javascript with the help of JQuery - this is basically what JSX is. We cursed it as bad due to no separation between UI definition (html) and code. We got given Webforms which did separate them. That lasted until we wanted to do proper MVC.
React just regurgitates all the bad practices of old. It should be banned because it is going to create a massive tech-debt problem very soon.
Vue did that, and it's so much better
Biggest fail that fb make is react, most people left platform because of slowness, but fb came all the ways possible like in the phones, etc that they continue expanding. But react get it self mostly fixed with hooks
I live and breathe React, React gave me everything I have today
React syntax and way of doing things is still shit. VUE is much better. I only HAVE TO USE React bcz of its wayyyyyyyyy larger ecosystem
@ any technology that has stayed for this long with a wide adoption simply buttresses React’s argument. React is not perfect but gets the job done.
Just came out of an interview and guess what it was all about? React!
@@uzochukwuamarabenneth2583 Yes. Only bcz of its adoption that I HAVE to use it. I hate it still even after 3 years
@@umer.on.youtube skill issue
You're Nigerian right?
I am currently learning react, can I get your twitter handle so you can help me out with my journey
It's still terrible and ugly
I am still thinking whether I should just learn JavaScript ONLY. I have many books and udemy course bought past 3 months, but still have the inertia to even look at the first pages. You see, I had to close my medical GP clinic few months ago and thinking that I could deal with Web programming which I hated. since late 1990s. My hobby thrill is just Linux and DBASE 2. Not knowing human race has just created a complexity, React. Have to learn Web for freelancing.
Even when I started i hated and leaved it, bit after some gap I retried & now I love it
I hated class based react too, it wasn't until functional state components that I started to appreciate React.