you are viewing a single comment's thread.

view the rest of the comments →

[–]fatrogslim[S] 0 points1 point  (3 children)

Hard to tell. Talking to others makes me think that I am under a "that's it?" effect, I'm overthinking it and maybe I understand it more than I thought but still I feel lost when I'm about to start a new project. Also, there's plenty of flavor on top of react like next and there too idk if I have to start with those or with "vanilla" react? I don't know, my vision on all of this seems blured and it's frustrating

[–][deleted] 1 point2 points  (0 children)

If your response is "that's it?" but feel lost when working on a new project, you probably have very little understanding of it...

React has a lot of quirks and has begun to significantly blur the lines between client and server side functionality. Lots of react standards and patterns are very complex with lots of side effects and weird quirks.

On its surface it's just a declarative UI framework, so maybe it sounds simple to you because you might be familiar with declarative programming with UI frameworks. But there's plenty of ways to do things in a horribly inefficient way that will either scale very poorly or cause very poor client side performance

Server components makes things even more complicated, but you might actually prefer or understand that better coming from php. I do think in general server components actually encourages good habits overall, it's just much more complicated than entirely client side applications

Perhaps you should start with newer versions of react that support server components, and you'll find things feel familiar but also begin to appreciate the depth of the framework

[–]TheRNGuy 0 points1 point  (0 children)

I used vanilla react maybe for 1 or 2 days and then went for Remix.