bug#34920: 27.0.50; Poor eww rendering of SourceHut file "trees"

[Lars Ingebrigtsen]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Not sure I understand why you think so: is it because of (1) the time wasted
> fetching it or (2) the slowdown imposed by parsing it or (3) the slowdown
> imposed on the rendering when the CSS is large or (4) ...?
>
> My impression is that just (1) would rarely be a performance
> problem (assuming it's just one CSS file)

It's seldom just one CSS file, and CSS files these days are often big
auto-generated monstrosities...

> and that the parsing could ditch all the irrelevant properties we
> don't support anyway so the impact of (3) should be minor.  So is it
> (2)?

(3) is minor, while (2) could be an issue.

But my point is that since we support very little CSS, spending time
fetching something that in 99% of the cases will make no difference to
our rendering is a disservice to the users.  eww is slow enough as it
is.

>> And asking web designers to change their pages so that they'll look
>> better in non-CSS browser isn't really scaleable.  :-)
>
> So what the solution?

Accept that most complex web pages will look like crap in shr and use it
for what it's suited for.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no