I thought immutable data structures and their identity checks actually are helpful re performance in react.
Why I don't use React
31–40 of 40 posts
Re: Why I don't use React
#32> I personally struggle with embracing immutability. Maybe that's because I'm more of a performance guy. Even though I really want to make my code more maintainable, and thus I started reading a lot more about FP in recent times. Honestly performance is a non-concern for me. I worked on a React app that ran on IE9 without any major performance issues and almost no code tuning. It's not even worth thinking about. Howe…
That seems to be a common attitude with front-end devs these days, to the detriment of web users. The performance impact of React, Angular, any other heavy frontend SPA framework is immense. Plus the extra weight required to get back to feature-parity with frameworkless (url rewriting, scroll reworking, etc). There are some complicated web apps like GMail where an SPA makes sense (although it's still super slow and h…
Can you share some React-based webapps that have poor performance?
Re: Why I don't use React
#33tl;dr I don’t use React because I don’t like immutability, it gives you bad performance (spoiler: it doesn’t). Also it’s from Facebook, everybody knows that Facebook is evil, hence React is evil. Really?
Also because I believed the FUD about its patent license. The patent license only ever granted rights compared to a BSD-licensed project without an explicit patent license.
Re: Why I don't use React
#34Earlier quoted context omitted.
I'm one of the people in that camp. I loved React, and still think it's a fantastic tool. A few things that have made me move on: - Svelte ( https://svelte.dev ) - People thinking Redux is brilliant. It's good, but it's a far too complex system to simply manage state. I'm aware this isn't React, but I have worked on very few React projects that don't have Redux - Run-time load. Back to Svelte. It's inspired me to rem…
I though svelte was interesting until I read a recent article where they introduced that `$:` label. It seemed like a very poorly thought out approach to me. That said, I honestly don't think I'll ever go back to using a framework with templates. My distaste for them has only gotten stronger the more I use React. > People thinking Redux is brilliant Redux is good as long as you understand what it's good for and only…
Having used a bit of Svelte 3, the label is quite easy to understand. On top of that, it's valid JS.
> Redux is good as long as you understand what it's good for and only use it when it buys you something. My default recommendation is to not use a state library until you find you need one.
Agree 100%
Re: Why I don't use React
#35The incessant >boldingwordreaditalics, the form of highlighting that doesn't jump out of the page at you.
Re: Why I don't use React
#36Why is this here? the article has no substance and it is poorly reasoned subjective preference.
Re: Why I don't use React
#37I clicked on it b/c it made to the front page and I read the entire article but I can't understand why he doesn't like to use react.
Re: Why I don't use React
#38Content-free article.
Lot of bold words though, and very distracting.
Re: Why I don't use React
#39Earlier quoted context omitted.
> I think it would be more interesting to read about people who know how to use it, have used it, but now choose not to. I suspect you won't find many people in this camp. I know a great many Angular->React converts, but very, very few lapsed React devs.
As an Angular developer I would be interested in reading some Angular->React conversion stories. I've dabbled in React a few times but it never felt compelling enough to switch, but maybe I missed the good stuff.
You should try Vue. I tried to use React a couple of times and never got the hang of it. With Vue however, you could say it was love at first sight (and I've heard some other people say the same)
Re: Why I don't use React
#40I think I'll write my own version of the article. I'll keep it more succinct though.
I like vue better.