On 2014-01-30 12:15:00, Jonas Smedegaard wrote: > Quoting Antoine Beaupré (2014-01-30 16:34:47) >> On 2014-01-30 09:29:08, Jonas Smedegaard wrote: >> > runtime pkgsize bloat: 0 >> >> Thanks for those measurements Jonas!! >> >>> If you insist on uglifying at runtime, then I still recommend >>> compacting CSS at build time (300 bytes win is silly when using >>> jQuery bloat!). >>> >>> If you insist on uglifying _CSS_ at runtime, then I still recommend >>> using ruby-sass, and switch to sassc later (see bug#694733,694730). >> >> I don't insist at all, in fact I don't understand why we would >> compress CSS at runtime at all. > > Ok. > > >> For JS it makes sense because of section 4.13 (convenience copies), but >> the CSS is native... > > Not sure I understand you here. Debian do not allow redistribution of > upstream-compressed JavaScript, but that does not force you to compress > at runtime: distributing buildtime-complressed JavaScript is fine to > distribute in Debian.
Right.
> Same is in principle true for CSS (and HMTL etc.) but less strongly
> enforced (because such declarative code is more likely to be still
> readable).
The difference being that the CSS is not "upstream" so we do not need to
fiddle around with symlinks. We can just shipped the compressed code in
the binary package and the original in the source without breaking
policy.
Of course, we probably want to ship the source CSS anyways as a
convenience to allow our users to modify it, but that's a separate
feature...
>> We could *suggest* an uglifier of some sort (and the jury's still out on
>> that I guess) but I strongly feel we should compress at build time.
>
> I don't understand what you are saying here. Are you distinguishing
> between "uglify" and "compress", about JavaScript and CSS, or only about
> buildtime and runtime?!?
I was specifically saying that we could allow users to modify the CSS
and recompress it, in which case we should Suggest: some kind of "CSS
compressor" so that this can be done easily.
But in my opinion, this shouldn't be a hard Depends: we should compress
at build time and not force people to install nodejs or ruby to use the
photofloat binary package.
If they want to edit the CSS and recompress it, then yes, they will need
to install one of those bundles, but we shouldn't enforce that if we can
avoid it.
A.
--
Be who you are and say what you feel
Because those who mind don't matter
And those who matter don't mind.
- Dr. Seuss
pgpgUeNSJm96s.pgp
Description: PGP signature
