I'm so impressed with your project's documentation (README), nicely done!
Show HN: Mega Boilerplate
21–30 of 57 posts
Re: Show HN: Mega Boilerplate
#22A small feedback: I just generated a React-based stack with a few Auth options - Email, Facebook, Google and Twitter.
The resulting `user.js` controller is 550 LoC.
It would be great if by default some of these logic are encapsulated in a service layer rather than littered in the controller itself. :)
Re: Show HN: Mega Boilerplate
#23Wow, as a long time RoR dev set in my ways, you may have finally given me the tool to overcome my laziness and check out this new fangled "server-side javascript" thing.
Re: Show HN: Mega Boilerplate
#24Re: Show HN: Mega Boilerplate
#25Re: Show HN: Mega Boilerplate
#26Awesome effort! I love the folder structure, very easy to follow. A small feedback: I just generated a React-based stack with a few Auth options - Email, Facebook, Google and Twitter. The resulting `user.js` controller is 550 LoC. It would be great if by default some of these logic are encapsulated in a service layer rather than littered in the controller itself. :)
Re: Show HN: Mega Boilerplate
#27Re: Show HN: Mega Boilerplate
#28I hate to sound negative, but what does it offer over yeoman and the individual generators out there? If I use a Mega Boilerplate setup, I lose scaffolding post-setup stage, so what do I gain?
I agree that it serves almost the same purpose, but for a beginner, seeing all the layers, what they do, and choosing them piecemeal is a great way to learn quickly before graduating to the yeoman ecosystem.
Re: Show HN: Mega Boilerplate
#29Express tip: add swig template engine
Angular tip: use a feature per folder structure for better componentization and "controller as" syntax (checkout John Papa's styleguide).