The layout is broken when viewed on mobile (iPhone 6). While this might seem like a minor nitpick, first impressions count.
You building a single page app from your iPhone?
Show HN: Mega Boilerplate
51–57 of 57 posts
Re: Show HN: Mega Boilerplate
#52Great 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.
Can understand that, but it does seem that hapi is gaining popularity, hope you'll reconsider!
Re: Show HN: Mega Boilerplate
#53I'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,…
> Possibly, but I think you underestimate the effort required to create and distribute a toolchain that would become shared and standardized.
Not really, because we're already doing it. It's definitely hard, but it's also definitely possible.
ember-cli has unlocked major community-wide sharing that is otherwise not possible. Like a healthy addon ecosystem (https://emberobserver.com) where things are far more likely to _just work_.
And this has kicked off a virtuous cycle. Big engineering organizations with long-term vision are joining in.
> become their "standardized" toolchain.
That's exactly the problem: once you create _your own_ standardized toolchain, you are the only one who can document it, teach it, ensure other things are compatible with it, and integrate upstream upgrades. When a community works together to decide on a much broader set of standardization, that burden is shared and everybody goes faster. And developer knowledge is much more portable.
Nobody making iOS apps thinks it's smart or necessary to write their own XCode. People writing ambitious web apps shouldn't either. (And I say that as someone who finds XCode annoying -- it's _still_ better than trying to build it yourself from scratch for each app).
Re: Show HN: Mega Boilerplate
#54Awesome! Will definitely use it for my next project!
Re: Show HN: Mega Boilerplate
#55I really like the design of this site. Is it full custom bootstrap?
Re: Show HN: Mega Boilerplate
#56I really like the design of this site. Is it full custom bootstrap?
I started with vanilla Bootstrap, but then it was iteration upon iteration of small UI changes. Here is how it looked in December 2015: https://twitter.com/EvNowAndForever/status/67842879978085171...
Re: Show HN: Mega Boilerplate
#57Would love to see an option to use Relay and GraphQL
I will consider adding it in the near future. It was originally on the roadmap, but don't have any experience with either Relay or GraphQL. In any case, I will open an issue on GitHub for this and do some research later.
That would be awesome! I've been working with Relay and GraphQL since they were released. Having messed with most of the boilerplates in that ecosystem, this one is the best IMO: https://github.com/fortruce/relay-skeleton
But I would love to see it with a testing framework, a css pre-processor and a production build script.
I'll track the issue and see how I can help.