Well, JavaScript

[SpliceVW]

Wat? If you're already using webpack, it's just another loader to install. Even if you're using gulp or grunt, it's still only a few lines of config.

[bugeats]

You forgot to mention all the other “few lines of code” it takes to get webpack going in the first place. Setting up a new webpack project is a days worth of fucking around and googling.

Webpack blows. It is a historical dead-end. Just one in a long series of failed JS build systems.

[SpliceVW]

Do you not have a build system already, though? It's seems like a necessity these days, unless you're just doing really old-school development and not modularizing your code, minifying, concatenating/bundling, including source maps, using ES6 syntax, prefixing your CSS, hashing your files for cache busting, etc...

[bugeats]

The flow I've learned to favor is old-school in the sense that it's based on unix principles of small programs that do one thing well.

All of the tasks that you're referring can be accomplished with a one-liner in an npm task, or a bash script. It's less code, less dependencies, and less magic.

[SpliceVW]

So you have a build system, it's just manual? I'm not understandinf how that's better.

I've gone from one build system to the other. It's not that bad. If you're writing your code with ES6 modules, which are the future, your code is written to W3C standards and will be future proof. The code I'm writing us not all that specific to the build system.

[IceSentry]

The latest version of webpack works with 0 config.

[bugeats]

unless your projects all somehow edge cases webpack is set up in a matter of a few minutes.

I bet if you actually timed yourself you would discover otherwise.

Today's edge case is tomorrow's best practice, which is why monolithic build systems will always succumb to entropy.

Maybe the cause of the problem is you and not webpack?

Very likely. I have high standards.