> (I say "my" because I'm sure my stack is different than yours in one way or another)
I think that's the problem. For a beginner what is their stack? It's a wild west of 'this months hip library' and for a beginner it's unintelligible.
> It's a wild west of 'this months hip library' and for a beginner it's unintelligible.
What's wrong with the "just pick one" approach??
Re:React/JavaScript fatigue
by pavel_lishin on Sunday December 27, 2015 @11:24PM
(#10799852)
Can you point me to one that'll help me actually get something workable up and running? You say you have one; I assume it's something you've put together over the time you've worked with React, and not something you just pull in from someone else's repo.
Re:React/JavaScript fatigue
by yazaddaruvala on Monday December 28, 2015 @01:14AM
(#10800131)
1. Do you have yeoman? http://yeoman.io/
2. I generally have `react-fullstack` installed
3. Run `yo react-fullstack`, `cd my_project`, `npm start`
Personally, I think its a bit overkill. I tend to delete most of it and add Bootstrap myself, but its a decent way to start a project.
Search for and pick a generator that suites your needs: http://yeoman.io/generators/
I find the overhead completely negligible. I've worked on many React apps. I've worked on innumerable apps in other, different frameworks, tools, etc. too. I still find my React stack (I say "my" because I'm sure my stack is different than yours in one way or another) to be the best solution, and this debate to be tedious.
That said, I feel like every ecosystems works this way: Complaints about lack of good tools/solutions, myriad tools/solutions are built, then there are complaints about the overabundance of tools and complexity of the ecosystem, so everyone abandons whatever the status quo is, and then...back to square one.