This is nice but it's not what I would call a "reset". It does make arbitrary choices for the value of some properties. It may be very good as "saner defaults", but for examples it doesn't even reset headers' font-size, or the margin above headers for example while it does reset the margin under headers (why?).

It's probably inefficient due to the use of the joker selector, but in modern CSS, I believe an actual reset would be as simple as:

    * { all: unset; }
    head, style, script { display: none; }

I don't think CSS resets make developing CSS easier for me... I'd rather have one set of bad defaults to develop on top of, than each project starting with its own set of good defaults that I then have to understand the strengths/weaknesses of every time.

Stuff affected by CSS resets rarely comes up when I'm sticking to the standard set of UI components for the project, and when it does, I need to do just as much debugging with the CSS reset as I would have to do without a reset.

Nice write up, very targeted at websites with a focus on typography. A more aggressive reset still seems appropriate if you’re building more in web app territory.

I follow this

https://www.joshwcomeau.com/css/custom-css-reset/

I never use CSS resets. Here's why: the

https://github.com/sindresorhus/modern-normalize

  The goal of this project is to make itself obsolete.

Modern CSS reset is Flutter