> You seem to be building an argument based on the idea that there's "one true way" to write web applications. Nah, you misunderstand me. I'm saying webpack+b

> You seem to be building an argument based on the idea that there's "one true way" to write web applications. Nah, you misunderstand me. I'm saying webpack+babel should be a single program with a sensible default config. I didn't mean to imply anything grander than that. > Choose the tools that suit you, learn them, and be happy. If someone decides to use Webpack+Babel, I don't think they're going to be "happy" about having to memorize a list of at least 9 different npm packages and 35 lines of configuration. Not to mention re-memorizing the new sets of packages and configurations every six months when some maintainer decides that package X should be split into packages Z, Q, and R, or that the current configuration tree is "wrong" and needs to be tweaked in backwards incompatible ways.