nice - could do with a none option on the template engine
It was originally there, but was later removed to keep things simple, specifically with rendering the initial React layout.
Show HN: Mega Boilerplate
41–50 of 57 posts
Re: Show HN: Mega Boilerplate
#42I'm going to go against the JS ecosystem grain and say that boilerplates are a total anti-pattern. And not because you should be doing this stuff by hand either, which is probably the second most popular answer. "Boilerplate" implies copying a bunch of code into your project that should be library code but isn't because it's too poorly designed to have an API cleaner than "just fork it, YOLO". It's dramatically harde…
> "Boilerplate" implies copying a bunch of code into your project that should be library code but isn't because it's too poorly designed to have an API cleaner than "just fork it, YOLO". It's dramatically harder to update than something with well-designed API boundaries.
In most of these cases, "boilerplate" implies a choice of frameworks, libraries, build and test tools, with a minimal or recommended configuration, all tested for interoperability. The actual code advancing your application is minimal.
In the case of megaboilerplate, it appears to be a mix of configuration files plus a mini hello world built on top of the technologies. The mini hello world seems to be mostly a demo of how the chosen technologies can interoperate, not really something that "should be library code".
> Shared, standardized toolchains are harder to build but once you do they're a dramatically better long-term investment.
Possibly, but I think you underestimate the effort required to create and distribute a toolchain that would become shared and standardized. In effect, a specific team might choose a particular boilerplate, tweak it to its needs, and the tools and libraries within that boilerplate become their "standardized" toolchain.
Re: Show HN: Mega Boilerplate
#43Am I the only one who likes to build his own projects from scratch?
Re: Show HN: Mega Boilerplate
#44The layout is broken when viewed on mobile (iPhone 6). While this might seem like a minor nitpick, first impressions count.
I don't see any layout rendering issues on iPhone 6s Plus/iOS 9.3.2/Safari Mobile. If you could open a GitHub issue and include a screenshot, that would be great.
Re: Show HN: Mega Boilerplate
#45I'm going to go against the JS ecosystem grain and say that boilerplates are a total anti-pattern. And not because you should be doing this stuff by hand either, which is probably the second most popular answer. "Boilerplate" implies copying a bunch of code into your project that should be library code but isn't because it's too poorly designed to have an API cleaner than "just fork it, YOLO". It's dramatically harde…
Agreed. I get so sad when I see this happen in the JS ecosystem (being used to python), but it's pretty easy to not fall into that trap. Use bower on the browser side, and npm on the server side. At that point, the only fight you have left is finding the stack of components that will play nicely together, which is the labor of architecture anyways.
Re: Show HN: Mega Boilerplate
#46Clicked and said "Ha, funny satire, boilerplates really ARE getting ridiculous", but from comments this is for real. Sounds good.
Re: Show HN: Mega Boilerplate
#47Page isn't loading for me. Github is though. https://github.com/sahat/megaboilerplate
Requests per second were going through the roof during initial announcement due to a lot of images, css, and javascript being served by the main Node.js app. Assets are now served from CDN, albeit hardcoded, but that I can fix later.
Re: Show HN: Mega Boilerplate
#48This is so awesome, great way to understand the current options and common choices in the ecosystem at a glance. I've been choosing Meteor recently precisely to avoid having to write a bunch of boilerplate Gulp/Grunt code to piece all the tools together and run the code and asset files through the pipeline.
Re: Show HN: Mega Boilerplate
#49Great project. Thanks for sharing! Any plans to add hapi as one of the framework options?
Re: Show HN: Mega Boilerplate
#50Great project. Thanks for sharing! Any plans to add hapi as one of the framework options?
I had originally started working on Hapi generator (there are still some leftover files in the Git repo), but decided against it after running a quick Node.js Framework survey among my Twitter followers. Given the amount of effort it would take to add a second Node.js framework and the low demand for it, it was simply not worth it.