Re:Did we reached webdesign's coolness boundaries?
by kedean on Wednesday November 25, 2015 @09:16AM
(#10627246)
That's not "atrocious css", that's minified CSS. They're running their backend code through a resource compression system like JAWR to conserve bandwidth. Who cares if the CSS that's presented to you isn't pretty, it's a declarative language anyway.
Re:Did we reached webdesign's coolness boundaries?
by paleite on Wednesday November 25, 2015 @09:14AM
(#10627237)
It's likely that's a remnant from Normalize.css (where each hack is assigned a number and an explanation) that didn't get removed when uglifying the CSS.
Re:Did we reached webdesign's coolness boundaries?
by criswell on Wednesday November 25, 2015 @09:20AM
(#10627256)
It's just minified. The CSS itself isn't terrible besides a couple overly verbose things, but nothing's atrocious. I think the /* 1 */ comment might reveal an issue with the CSS minifier they're using. That's normalize.css, all the other comments are removed besides the one inside a selector.
Why do they have this in the first block of text: /* 1 */
What's the point to commenting out the number 1?
I guess when they have a good lineup of speakers it doesn't matter? I don't know. I honestly don't know what to say.
So many questions, I don't know where to start.