Weirdan wrote:
Now, again, second way makes fewer assumptions about component environment so it's better™
Just got back from vactaion, and can't resist kicking the bee's nest....but here goes...
Better is very subjective, and if you're shooting for quick development time, making those assumptions will save the developer tons of time if their idea matches your assumptions. This is the big benefit from opinionated software. Opinionated software will make those assumptions at the expense of some extra work down the road if the developer wants to start deviating from the assumptions.
If you're building a framework to make websites, you might assume one single database, instead of multiple ones. You might assume the output's going to be HTML. You might even assume the framework to expect a few core tables to exist in the database.
"Better" means more in line with the goals you set out for your framework project. Quick development time, simplicity, and flexibility are usually at odds with each other. To me, it seems the skeleton folks are shooting for 1. Flexibility
2. Simplicity
3. Development Time
I tend to shoot for those in the opposite order of importance, and tend to recommend things accordingly.