Too bad I didn't catch this while it was still on the front page. I wrote Helium CSS a few years ago, https://github.com/geuis/helium-css https://github.com/ge

Too bad I didn't catch this while it was still on the front page. I wrote Helium CSS a few years ago, https://github.com/geuis/helium-css https://github.com/geuis/helium-css. There are many problems with the approach being taken with MinCSS that are reflected in how Helium was constructed. 1) Server-side parsing is brittle. Using regex's for this is a no-no. Helium uses document.querySelector in the browser to really test if a selector matches or not. It even has Sizzle for older browser support. 2) Different css is used to target different browsers, or at least different capabilities. Running this server-side doesn't tell you which browser some totally valid css is meant to be used for. 3) Removing un-matched css rules by default is a no-no. Again, tools like this can be clever but they're never smart. It takes the engineer's eye to say, "This is something I actually need to keep" or "Yup, remove this". 4) Helium works in the browser. This lets you easily run it across multiple browsers that you need to support. You could make a headless browser that uses Helium, but you're going to be limited to Webkit (phantomjs). Its a thought I've had, but never really thought it was worth the trouble of building such a limiting system. I encourage anyone who needs a versatile tool to try Helium. Feel free to contribute patches and stuff.