React Conclusion: Remove reference to metaframeworks and server components

nikitarevenco commented 3 months ago

Checks

[X] This is not a duplicate of an existing issue (please have a look through our open issues list to make sure)
[X] I have thoroughly read and understand The Odin Project Contributing Guide
[X] Would you like to work on this issue?

Describe your suggestion

I feel like the following two paragraphs:

Frontend is the land of innovation, and React is one of the leaders in the space. You can keep up with the future of React by following the React RFC GitHub repository. This is where new features and changes to React are proposed, discussed, and eventually accepted or rejected. One of the groundbreaking RFCs is Server Components. Over this course, we've rendered our React components in the client, but here this RFC discusses how we can bring React to the server and render it there. This feature has huge potential and is worth keeping an eye on in the future.

Furthermore, you can dive into React meta frameworks. They're a framework for React that add first-class support for functionalities like data fetching and routing. Additionally, they leverage React's latest features to provide the best experience possible for developers and users alike. Some examples of these are Next and Remix.

Can distract learners from continuing TOP and learn about the metaframeworks instead. It's definitely a rabbit hole. I'm speaking from personal experience -- The above two paragraphs are what caused me to become more interested in nextjs, react server components and all that stuff. i did a lot of research and eventually stopped TOP to learn about those frameworks instead. It's like butterfly effect.

Well, I think if TOP wants learners not to deviate from the course it would be wise to remove those two paragraphs. I think it could be nice to add them at the end of the node course instead, maybe.. but this could also be just me. I'm only throwing this out there

Path

Node / JS

Lesson Url

https://www.theodinproject.com/lessons/node-path-react-conclusion

(Optional) Discord Name

No response

(Optional) Additional Comments

No response

KevinMulhern commented 2 months ago

Thanks for the suggestion @nikitarevenco, can someone from the @TheOdinProject/react team take a look at this please?

MaoShizhong commented 2 months ago

Thanks @nikitarevenco

I would not be opposed to a softening of those parts mentioned, as I agree they do sound quite encouraging to rabbit hole into. This is less of a problem in the Rails pathway since the React course is the final course there (besides Getting Hired). Less so in the Node pathway, since people may consider diving into full stack metaframeworks and all that jazz before even learning about the backend, and we have had a few questions regarding the Node course about why we teach Express and not NextJS etc. (further fuelled by not understanding core concepts).

I would like to keep the soft suggestion of following the React RFC repo, but just framing the stuff after in a more "it's nice to know what's going on with the tools in the real world/keep up to date" sort of thing. I don't feel like we need to directly link to server components nor explain what they are. Perhaps "...and eventually accepted or rejected, such as features like server components." Having a nosy at what's going on in OSS and stuff has been something that's fuelled a lot of my interest and excitement, and I feel there's less harm than good in just keeping up to date with news.

For meta-frameworks, I'm not too keen on the "...you can dive into..." wording, again, more so for the Node path than the Rails path. Perhaps rewording that paragraph just to mention that there are "meta frameworks" for React that build on top of it further, which may be of interest after finishing the curriculum. Leave it simply as an informative bit with an "after the curriculum" suggestion to fit both pathways.

What do you think?

nikitarevenco commented 2 months ago

Thanks @nikitarevenco

I would not be opposed to a softening of those parts mentioned, as I agree they do sound quite encouraging to rabbit hole into. This is less of a problem in the Rails pathway since the React course is the final course there (besides Getting Hired). Less so in the Node pathway, since people may consider diving into full stack metaframeworks and all that jazz before even learning about the backend, and we have had a few questions regarding the Node course about why we teach Express and not NextJS etc. (further fuelled by not understanding core concepts).

I would like to keep the soft suggestion of following the React RFC repo, but just framing the stuff after in a more "it's nice to know what's going on with the tools in the real world/keep up to date" sort of thing. I don't feel like we need to directly link to server components nor explain what they are. Perhaps "...and eventually accepted or rejected, such as features like server components." Having a nosy at what's going on in OSS and stuff has been something that's fuelled a lot of my interest and excitement, and I feel there's less harm than good in just keeping up to date with news.

For meta-frameworks, I'm not too keen on the "...you can dive into..." wording, again, more so for the Node path than the Rails path. Perhaps rewording that paragraph just to mention that there are "meta frameworks" for React that build on top of it further, which may be of interest after finishing the curriculum. Leave it simply as an informative bit with an "after the curriculum" suggestion to fit both pathways.

What do you think?

Agreed. Looks like removing direct references and making the wording a bit more general is the right approach here. Encouraging interest is healthy if its not overdone. I'll PR this with an initial draft

MaoShizhong commented 2 months ago

Cool, I'll assign you then @nikitarevenco

TheOdinProject / curriculum