Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What CSS minifiers also leave behind

luisant.ca

Post reply on HN
Print view View original

101–109 of 109 posts

Re: What CSS minifiers also leave behind

#101

Post by remy_luisant »

greenshackle2 wrote: post #61
remy_luisant wrote: post #5

Earlier quoted context omitted.

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…

You're being silly, I'm a self-taught Python coder with a degree in agricultural engineering , a sprinkling of C, Linux, Lisp and statistics, almost no JavaScript, I'm headstrong and I dress like shit, and I still managed to find interesting opportunities in the job posting threads here. Just post your damn CV.

Right. You guys are right. I'll do that next time around.

Re: What CSS minifiers also leave behind

#102

Post by Nadya »

masklinn wrote: post #17
legulere wrote: post #15

Earlier quoted context omitted.

Scientific notation seems to be part of CCS3: https://www.w3.org/TR/css3-values/#numbers Which browser had problems with it?

"q" is also CSS3, incidentally, and its background is interesting[0]: it's a mostly japanese metric typographical unit[1], it replaces the point, and is slightly smaller: q is 0.25mm while pt is ~0.3528mm (precisely 1/72th of an inch which is 25.4mm). [0] http://tosche.net/2013/10/font-size-in-the-metric-system_e.h... [1] although non-japanese typographers like Otl Aicher have recommended its use it doesn't seem to h…

"q" is not supported in the latest version of Chrome but is supported in Firefox. I'm debating using it on my site just to get a few headscratchers. Also to play off the weeb factor a bit as a joke. Thanks for introducing it to me.

Now to debate whether or not adding 3 lines of my CSS for a joke is too much.

Re: What CSS minifiers also leave behind

#103

Post by bostonvaulter2 »

jwilk wrote: post #26
cperciva wrote: post #2

I'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.

Pro tip: you can increase your chances of getting hired by 4.2% by not saying Le Sigh .

Maybe he's actually filtering out employers

Re: What CSS minifiers also leave behind

#104

Post by remy_luisant »

bostonvaulter2 wrote: post #103
jwilk wrote: post #26

Earlier quoted context omitted.

Pro tip: you can increase your chances of getting hired by 4.2% by not saying Le Sigh .

Maybe he's actually filtering out employers

I am. It won't work if the employer is not silly/carefree enough.

Good fucking luck, no? :P

Re: What CSS minifiers also leave behind

#105

Post by remy_luisant »

cperciva wrote: post #2

I'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.

https://luisant.ca/Remy_CV_public.pdf

Well, fuck my life. Here goes, posted on the site too.

This required way more courage than anything else I have done in the last few months, even after I censored it to death.

Thanks for the good words, guys. I know you are right. Even though I hate to agree with you, you are right. I hate to do this, but you are right.

So it is done.

Re: What CSS minifiers also leave behind

#106

Post by thaunatos »

remy_luisant wrote: post #96
phire wrote: post #40

Earlier quoted context omitted.

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…

I'm working on one, though I'm not sure if it will ever see the light of the day. I have four months of free time and if someone would feed and house me for that time, I'd do it and open source it. Any sponsors? No? Didn't think so. Not even you, big G? Aww... For now some minifiers do sort the values, which helps.

Maybe open-source it anyways? :-)

Re: What CSS minifiers also leave behind

#107

Post by remy_luisant »

thaunatos wrote: post #106
remy_luisant wrote: post #96

Earlier quoted context omitted.

I'm working on one, though I'm not sure if it will ever see the light of the day. I have four months of free time and if someone would feed and house me for that time, I'd do it and open source it. Any sponsors? No? Didn't think so. Not even you, big G? Aww... For now some minifiers do sort the values, which helps.

Maybe open-source it anyways? :-)

I won't have it any other way.

The "not starving to death" thing is a bit of an issue on the way there... Well, I have savings, but...

And if I get a horrid job, then I won't have the energy. :P

Re: What CSS minifiers also leave behind

#108

Post by flukus »

camus2 wrote: post #23
flukus wrote: post #11

Earlier quoted context omitted.

The other benefit is from combining files and reducing the number of http requests. Minifiers are really needed for that, but the do make for some nicer development workflows.

> The other benefit is from combining files and reducing the number of http requests. Minifiers are really needed for that, but the do make for some nicer development workflows. debatable with HTTP2 . Furthermore, separate files are easier to cache. If one of them doesn't change it doesn't have to be loaded again. That's my experience with bundles, especially when one uses asynchronous module definition instead of ba…

What about cache expiry? Minfiers can generate a hash and tack that on to the file name so it's cached forever. With http2 can you do this without the back and forward conversation?

Re: What CSS minifiers also leave behind

#109

Post by cfqycwz »

bastawhiz wrote: post #78
cfqycwz wrote: post #59

Earlier quoted context omitted.

Anybody know if the transparency one is actually a desirable optimization? Iirc, you might want to assign a color to your transparency so it's not shifting hue as you fade it in through CSS transitions, animations, or JS.

Author of crass here. That's interesting: if you have a specific case where the browser doesn't do what you'd expect, I'd love to see it in a Github issue! https://github.com/mattbasta/crass/issues/new

I was thinking of the fact that transparent is supposedly an alias for rgba(0,0,0,0), but this doesn't seem to cause an issue when I try it out, in Firefox at least.
Post reply on HN