Hacker News Reader

Comment by zzalpha | Hacker News Reader

Meh, if it means rapidly putting together a high-quality, cross-browser, responsive website with little effort, I'll accept a little bloat. The savings in developer time is more than worth it, IMO. Doubly so given how much of that CSS and JS is likely cached.

View on HN

For prototyping this is okay. But for production I try to keep bloat as low as possible. I see this as service to my customers. A fat ui framework like this adds its very own complexity and as soon as you want to go out of the crud box you will have to add your own styles anyway.

You can cut the unused styles out after.

I try to get my bloat down, I just load the components which I'm going to use (most of the time it's the grid).

There are some tools like purifycss [1] which can delete unused css

1: https://github.com/purifycss/purifycss

Indeed an interesting tool. If one keeps the site structure simple enough I think that the no-framework way might fit best. One doesn't have to go as far as for example this site http://bettermotherfuckingwebsite.com but it made me think about minimalistic css while keeping great device support.

I recently read the blog (http://.ws) of Adam Morse (http://mrmrs.cc) and it gave me some inspiration for my own css stuff.

I didn't compare the results between Purifycss and this bash script[1] yet. But this alternative, not intent to compete, does mainly the same detection e.g. including dynamic class adding detection.

1: https://gist.github.com/50kudos/3028fac585eda85aea9a

Reply on news.ycombinator.com