Speeding Up a Fat Web Client

Re:Speeding Up a Fat Web Client by tzahola on Sunday October 22, 2017 @08:15PM (#15529806)

2 mbytes of CSS? Wtf. I’m genuinely looking forward to the day when Moore’s law finally fails, and puts an end to this madness.

[ Parent | on HN ]

Re:Speeding Up a Fat Web Client by robocat on Sunday October 22, 2017 @09:42PM (#15530101)

They reduced the CSS by 2MB (uncompressed), that says little about how many MB remained.

[ Parent | on HN ]

Re:Speeding Up a Fat Web Client by aptwebapps on Monday October 23, 2017 @01:20AM (#15530891)

I see two files totaling about 1.5 MB when uncompressed.

[ Parent | on HN ]

Re:Speeding Up a Fat Web Client by jlebrech on Monday October 23, 2017 @05:30AM (#15531861)

you could reduce the complexity of the selectors by converting everything to id selectors, that would also end up bloating the css, but offsetting cpu usage to memory usage.

[ Parent | on HN ]

Re:Speeding Up a Fat Web Client by amiga-workbench on Monday October 23, 2017 @04:07AM (#15531552)

It won't, sites will just swell up to 10MB of CSS.

[ Parent | on HN ]