Hmm, well I don’t know that that’s what I meant. I think some of my earlier replies were a bit dumb.
I honestly think that this thread is pretty muddy and hard to get a good picture of. Some folks seem to have the position that most of the deps in a new project shouldn’t be there (and instead should be deps if ember-cli), others are saying it’s hard for someone quite new to programming to get a handle on all the moving parts (what’s needed, what’s not, how it all works), and still more are focused on teaching folks how to figure out what things do as that skill will likely have a larger impact on folks than just explaining a specific set of dependencies.
I’m not terribly qualified to answer all of these questions (I’d suggest perhaps none of us are), and I definitely don’t want to get mired in an unresolvable argument.
I really don’t know, but I certainly wouldn’t want to work in an app like this. Being either completely locked in (if the other deps were hoisted and always forced on you) or having so little out of the box capabilities (no transpilation, no fingerprinting, no minification, etc).
Can someone explain why the count of dependencies matters?