News for hackers. Stuff that matters.
Re:React/JavaScript fatigue by masonicb00m on Monday December 28, 2015 @01:08AM (#10800113)
Nodded my head all through the article. Project setup hurts. "What folder do I put my components in? Even the ones that only get used on one page?"

We need a DHH.js to rise up and bring us "Rails, for React".

Re:React/JavaScript fatigue by Corrado on Monday December 28, 2015 @04:27AM (#10800492)
Opinionated programming was/is Rails' major contribution to the web world, as far as I'm concerned. By providing a baseline of things you need (directory structure, modules, logic flow, etc.) it made starting a project easy. In fact, it's just a single command.

I think having all of these (ever changing) options is a sign of Javascripts immaturity; it's not bad, it's just growing pains. Hopefully someone will step up with a cookbook of best practices which will be respected and used throughout the community.

Re:React/JavaScript fatigue by lopatin on Monday December 28, 2015 @01:13AM (#10800126)
I put my components into app/components. This is the one, true directory structure. All other directory structures are wrong. \s