What CSS minifiers also leave behind
91–100 of 109 posts
Re: What CSS minifiers also leave behind
#92I'm for hire now. Le Sigh. Email's in the footer. Remy: I'd suggest posting a CV and linking to it from this post. I looked and couldn't find one anywhere on your site; you'll get a lot more qualified interest if people can find out more about you than just a few blog posts.
I thought about it, but I'm way too shy for that. Not like it would lead to anywhere either, you know. :P Two years of teaching university, MSc in computing, love of automation, combinatiorial optimization without any significant amount of deep math skill, circuit design, gate array stuff, low-level CPU optimization stuff, hardware counters, microcontrollers, SQLite, Julia language, C, shell, a bunch more programming…
Seriously, if you want a job, publish your CV on your website already.
Re: What CSS minifiers also leave behind
#93Author here. Wow. #1 on HN. Wow. I'd usually hang around a bit more, but I'm really tired. I posted this past my midnight. 00:51 now, and I'm fading fast. Thanks for all the love, everyone. I'll come over tomorrow (12 hours from now, or so) to answer any questions or to pick up any corrections.
I hope you sleep well.
Re: What CSS minifiers also leave behind
#94> I'm guessing that at nine nines that is pretty much a one anyway and it would not even change a single pixel on the screen. There used to be a bug with flex-wrap: wrap; where an element would wrap to the next line while it should have fit. You could fix it by instead using width: 25%; use width: 24.999999%; so it would be 25% on the screen but it would fix the problem so it didn't wrap to the next line. So you shou…
Re: What CSS minifiers also leave behind
#95Re: What CSS minifiers also leave behind
#96Don't mean to squash any enthusiasm, but these types of 1byte optimization savings don't really have real-world benefits due to over-the-wire compression like gzip and Brotli. A more interesting problem to solve, I think, is that of optimising CSS rules for browser rendering.
I think that there is merit in designing a minifier that is explicitly designed to optimise the gziped size rather than the uncompressed size. Things like: * Rearrange rules within the file to put similar rules within the sliding window. * Rearrange rules so that tail of the last declaration of one rule and the start of the next selector create the longest possible common substring. * Rearrange the order of declarati…
Any sponsors? No? Didn't think so. Not even you, big G? Aww...
For now some minifiers do sort the values, which helps.
Re: What CSS minifiers also leave behind
#97crass is doing some really wonderful stuff here -- I'm impressed! It's very interesting, however, that no one minifier is a consistent winner in these test cases, and that running CSS through multiple minifiers is actually, potentially, not all that crazy. (The very debatable real value in doing that notwithstanding.)
I appreciate the compliment! (author of crass here) I've mentioned it before, but it's really not a great idea to use multiple minifiers. Minifier bugs can get nasty, and using multiple minifiers exponentially increases the likelihood that you'll encounter some weird or broken behavior. Make sure to test thoroughly.
Re: What CSS minifiers also leave behind
#98I like your site design. Very clean and readable.
My pleasure! All from scratch, designed for nothing but readability.
I am building textbooks on the same code, so the blog is a great stress and user test.
Re: What CSS minifiers also leave behind
#99Can someone provide some hard numbers from real projects as to is it really worth it assuming we can gzip/brotili?
Re: What CSS minifiers also leave behind
#100I liked the writing style, fun read AND very informative!