26 comments

[ 2.8 ms ] story [ 57.1 ms ] thread
This is awesome. One thing though. Instead of having to wait for the results to be calculated how about emailing the results when it's done? That way there's less need to keep the page open.
Good idea, especially with the HN traffic overloading my worker dynos right now. I'm scaling them up, but I'm afraid what this might cost...
Also what about caching past queries for X days?
Why not use the users browser itself to calculate the results?
Totally killed all of my media queries..

http://jairaj.org http://www.csstrashman.com/styles/495

Yeah, it's still beta. It's powered inside by this open source library https://github.com/begriffs/css-ratiocinator

Please submit issues on github and I'll work on addressing them.

Hi,

"Ratiocinator" is a nice name. Is "begriffs" a reference to the Begriffsschrift ?

Yes it is! This is kind of nerdy, but I have a picture of Frege hanging on my wall for inspiration. :)

Is Saint-Loup a reference to Proust's friend?

breaks:

  <title>Application Error</title></head>
    </head>
    <body>
      <iframe src="//s3.amazonaws.com/heroku_pages/error.html">
        <p>Application Error</p>
      </iframe>
    </body>
Surprised to get a message about being in a queue. Have they heard of concurrency? Lots of people are doing it. Unless I dont understand what they're doing (Always a chance of that).
Sorry for the outage. I ran past the free-level heroku db capacity. It's upgraded and the site is back up.
Could you add an email field so it emails us when the job is done?
Wouldn't it be better to use a random hash string for the resulting URL or none at all instead of a continuous counter which is incremented?

I can easily walk through the submission and see the used URLs.

But maybe that's just exaggerated.

I have no problem waiting if the thing actually works and will clean up my css. After implementing the new styles, is it looking just as good?
Sorry, I don't get the point of this. It took my CSS with related rules grouped together and spread them all over, and expanded my shorthand CSS into longhand. The file size change was minimal.

Also, telling people "your X is garbage" isn't the best way to greet your users.

Try not to take it personally. Maybe you're not the target market.
Not using a CSS rule in a single page doesn't mean you don't use it elsewhere => the generated CSS is necessarily wrong.

This tool is useless but being a POC.

Exactly. I minify my site's CSS but there are rules used on only some pages. Unless you crawl the whole of a website, this tool is useless for any site that has more than one page.

You'd be better off using SitePoint's DustMeSelectors as it at least makes an effort to crawl the site's CSS: http://www.sitepoint.com/dustmeselectors/

(bit out of date though, it seems)

It's a nice idea, but it broke both sites I tried it on. I'm happy to supply bug reports if that'll help.
In what sense is using absolute pixel values in your CSS better than using percentage of the parent element or em's? Last I checked, it was the other way round.