Comment by ksec

To be fair, Safari 18 ( finally ) improved a lot on what what reported in both State of CSS and JS. With 26 even better, it is gotten to the point where I believe hopefully 27 it will be a non-issue most of the time. As long as they continue to grind through everything for the next few years and not stop / pulling out resource on Safari Team.

Agree on the time/performance budget. It is pain stupid. As has been the case for so many years. And yet nothing has been done about it.