3 ms·

> You can learn React in a day. Maybe React itself, but everything else that goes into doing react development; design patterns, gotchas, testing, webpack, nat

> You can learn React in a day. Maybe React itself, but everything else that goes into doing react development; design patterns, gotchas, testing, webpack, native and so on? That takes far longer than a day, and is what most would expect when being able to really say they "know react".

chatmasta 9y ago
Agreed, but as I mentioned in my edits of the comment, you’ll likely end up needing to solve all these problems in vanilla JS as well. So it’s really a question of picking your poison. Also, many of the concepts you need to learn for proficient react development are auxiliary to react and could be applied to vanilla JS or really any UI framework. Any UI is fundamentally a state machine, and solutions to implementing it all require state management and clean separation of the presentation and data layers.
dictum 9y ago
I don't want to turn this into another misguided "JS sucks" thread[0], but here's an example from create-react-app, the official point of entry for people learning React: https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md https://github.com/facebook/create-react-app/blob/master/pac... The README included on a project generated through CRA is 116KB. A screenshot of that page rendered in GitHub is 60054px tall. Honestly, I don't know if this could be made simpler or easier. React and its ecosystem deal with complex problems that can't always be reduced to simple explanations. In the case of this README, of course a lot of it is about specific setups that most beginners don't need to care about, but that CRA, being the blessed point of entry, still should support, or it would lock everyone into a Facebook workflow. I think many developers would be better served by entering frontend development not through React, but through the basics (HTML, CSS, JS) and other ecosystems. [0]: Unrequested opinion: frontend developers reach for bigCo solutions — whatever Facebook/Google/some billion-dollar startup uses — when smaller, lesser known, "boring" or exploratory solutions could be better, trying to solve problems they don't have.
- symlinkk 9y ago
  That's not the official point of entry, the main React site is: https://reactjs.org/docs/hello-world.html https://reactjs.org/docs/hello-world.html
  - dictum 9y ago
    Good point. What I meant by "point of entry" wasn't the way to learn React as an absolute beginner, but the official tool to use after you've learned the basics of React itself. A beginner can (and should) go far without a build system.
dmitriid 9y ago
Yeah, and how WebComponents are gonna help with that? Considering that you need all of that just to make them marginally useful.

chatmasta 9y ago

Agreed, but as I mentioned in my edits of the comment, you’ll likely end up needing to solve all these problems in vanilla JS as well. So it’s really a question of picking your poison. Also, many of the concepts you need to learn for proficient react development are auxiliary to react and could be applied to vanilla JS or really any UI framework. Any UI is fundamentally a state machine, and solutions to implementing it all require state management and clean separation of the presentation and data layers.

dictum 9y ago

I don't want to turn this into another misguided "JS sucks" thread[0], but here's an example from create-react-app, the official point of entry for people learning React: https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md https://github.com/facebook/create-react-app/blob/master/pac... The README included on a project generated through CRA is 116KB. A screenshot of that page rendered in GitHub is 60054px tall. Honestly, I don't know if this could be made simpler or easier. React and its ecosystem deal with complex problems that can't always be reduced to simple explanations. In the case of this README, of course a lot of it is about specific setups that most beginners don't need to care about, but that CRA, being the blessed point of entry, still should support, or it would lock everyone into a Facebook workflow. I think many developers would be better served by entering frontend development not through React, but through the basics (HTML, CSS, JS) and other ecosystems. [0]: Unrequested opinion: frontend developers reach for bigCo solutions — whatever Facebook/Google/some billion-dollar startup uses — when smaller, lesser known, "boring" or exploratory solutions could be better, trying to solve problems they don't have.

symlinkk 9y ago
That's not the official point of entry, the main React site is: https://reactjs.org/docs/hello-world.html https://reactjs.org/docs/hello-world.html
- dictum 9y ago
  Good point. What I meant by "point of entry" wasn't the way to learn React as an absolute beginner, but the official tool to use after you've learned the basics of React itself. A beginner can (and should) go far without a build system.

dmitriid 9y ago

Yeah, and how WebComponents are gonna help with that? Considering that you need all of that just to make them marginally useful.