11–20 of 57 posts
I 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?
At least the AngularJS + NodeJS boilerplate isn't using the latest suggested style guidelines and folder structure. But great first start!
I 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.
As a predominantly backend developer, If I just want to have a 2016-style workflow for the frontend part of my site, it's really hard!
The layout is broken when viewed on mobile (iPhone 6). While this might seem like a minor nitpick, first impressions count.
B. "iPhone 6" says nothing about what browser or iOS version you are using.
I 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.
With the boilerplate I was locked into the questionable decisions and brittle implementation of the original author. Changing anything usually broke my app and because I had taken the starter kit shortcut I didn't have the understanding of how to fix it.
Earlier quoted context omitted.
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.
I used React Starter Kit for a project and greatly regretted it. In the end I would have been better off taking the time to learn how the parts fit together myself. With the boilerplate I was locked into the questionable decisions and brittle implementation of the original author. Changing anything usually broke my app and because I had taken the starter kit shortcut I didn't have the understanding of how to fix it.
What I like about the site is the visualization.
So, for instance, you know that Express is an alternative to Meteor, not a complement. And that Jade/Handlebars work with Express and are alternatives to each other.
Just having that for all the combination of names is valuable.
Basically, it helps you understand the taxonomy.