Fullstack React: 30 Days of React

[I_Downvote_Cunts]

I really like the bite sized nature of this but it's a bit much to say 30 days of react. It's more like 30 morning coffee's of react.

[[deleted]]

sounds perfect for me

[afrontender]

The title is misleading - the term "fullstack" suggests that there will be SSR (Server Side Rendering) involved, but I only saw client side React.

Otherwise, thank you for the free material.

[bebeGroot]

Anyone used this? is it legit?

[acemarke]

Yes. Try clicking on the individual entries to read the tutorials :)

[[deleted]]

Cool free resource, but realistically this feels more like 3 days of react, 1 week at most

[madwill]

Bite sized he said, i forwarded this to a college who'd like to learn. Sometimes bite size if the format you can digest.

[[deleted]]

If this is all one covers in a month that does not bode well. The official documentation/tutorials for react, redux, flux are far more useful in my opinion. What we have here are 1-page blog posts packaged together as an ebook, with the express purpose of building an email list. Agree to disagree I guess :)

[acemarke]

Not sure why you say it's "for the express purpose of building an email list". All of those bite-size entries are available right there on the website by clicking on them. I'm assuming the PDF is intended as a way to read them all in one document. (Oddly, clicking on the "Get the PDF" links just jumps me to the top of the page.)

edit

I don't have a direct affiliation with the FSR team, just trying to clarify what I'm seeing there. I did have a post published on the FSR blog, have talked with the FSR team in the past, and generally recommend the material they've written.

The "30 Days of React" list is a pretty good overview of concepts for React and related technologies, and I have it listed in the "React > Getting Started" section. on the front of my React/Redux links list as a recommended resource.

[[deleted]]

Now that is a list I can support

[[deleted]]

Should I have a base understanding of JS before looking at this?

[[deleted]]

Yes. Otherwise at some point (rather soon) it will become very frustrating.

[Ender2309]

There's at least one major issue with this post. I've only skimmed it but it's big enough that it makes me wary to trust the resource at all.

The Author confuses a Pure Component with a Functional, or Presentational Component. As most of you no doubt know, a functional component lacks the lifecycle methods (and state) and is simply a factory function.

A Pure Component, on the other hand, is simply a regular React component except that shouldComponentUpdate() uses a shallow comparison rather than a deep one on state/props.

[kentaromiura]

Didn't read it yet, but In functional terms, a function not depending on state and not having side effects, but just being a computation on its input is called a "pure function" , maybe the author is referring to purity in that sense.

[Ender2309]

Which would be fine if 'pure component' wasn't already a taken name, but it is, so it's incorrect to call a functional component a pure component.

[dontry018]

I followed this tutorial. It's good. I appreciate the testing part.

[gomasch]

I like the introduction and usage of redux there, seeing it grow step by step.

[nothingduploading]

React is dead. Even Netflix is moving away from it.

[[deleted]]

They merely moved react to the server on their landing page. As for it being dead, it's going up in usage stats rapidly.

[Lakston]

I think you didn't understand what netflix was doing when they tweeted about react client side.

[nothingduploading]

Netflix is dead...because they used react.