Hacker News Reader

Thanks for the input! I've been debating the merits of minifying HTML, CSS, and JS. I learned about all three of those extensively by exploring others' code. Minifying breaks that. How do you address that issue?

View on HN

Breaking the readability is the trade-off you have to make, though I think it's worth it for production code, it really brings the file sizes down and if you concatenate all your javascripts in to a single file you can really cut down on requests too.

If you use Google chrome you can click the '{}' icon inside the developer tools to 'pretty print' the javascript which helps a little!

There's also JavaScript Source Maps which you might want to look in to: http://www.html5rocks.com/en/tutorials/developertools/source...

You only minify the deployed CSS and JS, so in development, it's still perfectly readable. You shouldn't really need to read production js, usually, and when you do (for debugging issues that only happen in prod), the little brackets in Chrome that my sibling pointed out will be enough.

Reply on news.ycombinator.com