Most with absolutely zero data to back up that it provides any sort of useful improvements to justify the difficulties it introduces in debugging.
Considering how almost all web-servers and browsers support HTTP compression, minification is mostly a cargo-cult ritual.
jquery-2.0.3.js 236K
jquery-2.0.3.js.gz 70K
jquery-2.0.3.min.js 82K
jquery-2.0.3.min.js.gz 29K
Minification pay off a lot even with compression. time curl http://code.jquery.com/jquery-2.0.3.js > /dev/null
real 0m0.433s
time curl http://code.jquery.com/jquery-2.0.3.min.js > /dev/null
real 0m0.210s
Is it proved now ?Edit: Off course I didn't ran these requests only once.
time curl http://code.jquery.com/jquery-2.0.3.js > /dev/null
236k bytes
real 0m0.432s
time curl http://code.jquery.com/jquery-2.0.3.min.js > /dev/null
83612 bytes
real 0m0.323s
time curl http://code.jquery.com/jquery-2.0.3.js --compressed > /dev/null
87509 bytes
real 0m0.273s
time curl http://code.jquery.com/jquery-2.0.3.min.js --compressed > /dev/null
34066 bytes
real 0m0.215s
I think that people should be more skeptical of the complexity introduced by things like minification, but the advantages are pretty clear, even with compression.While it depends on a lot of factors, generally speaking minification is a good thing especially for mobile. There's really no downside in doing it (see next point).
> justify the difficulties it introduces in debugging
What difficulties? You should use a build process that minifies for your production site but not for testing. If you need to debug the live, minified files you can use source maps[1].
1: http://www.html5rocks.com/en/tutorials/developertools/source...
A quick google search got me to SO: http://stackoverflow.com/a/807161 results seem pretty significant. Besides, the worse your connection is, the more you will appreciate these techniques.
The packaging and minification can be handled either as a filter at the server level or during the build and deploy if your stack supports that metaphor. These have been the common practices in my experience.
So unless you re-implement the minification algorithm to be optimised for minimising diffs you might find that every variable's name has changed and size of the file diff might start to approach (or exceed) the size of the file itself.
I'm not saying it's a bad idea, but starting with a case study would be nice rather than jumping in with "we've completely changed everything about how script files are delivered, it's amazing and we have cool graphics to prove it". The dinosaur looks a bit hand-wavy.
There are a lot more moving parts, a lost more surface area for things to go wrong, etc. Yes, downloading huge JS files is a problem, but you're going to have to download them one way or another.