Re:Show HN: Reactuate – a React/Redux stack with a focus on ...
by lf-non on Monday February 01, 2016 @05:11AM
(#11010865)
This has been my primary concern and the reason for which I avoid boilerplate kits except to study them:
> Fork-and-forget (or fork-and-follow) is not a great way to keep up with what's happening in the original boilerplate (and in the space in general). Therefore, starting off a cloned boilerplate "kit" is not an acceptable solution. Reactuate is distributed as a dependency.
I am interested in understanding why the author chose not to use yeoman ? Wouldn't it be nice to get things like support for interactive generators for free -- while retaining the ability to compose and update ?
> Fork-and-forget (or fork-and-follow) is not a great way to keep up with what's happening in the original boilerplate (and in the space in general). Therefore, starting off a cloned boilerplate "kit" is not an acceptable solution. Reactuate is distributed as a dependency.
I am interested in understanding why the author chose not to use yeoman ? Wouldn't it be nice to get things like support for interactive generators for free -- while retaining the ability to compose and update ?