My VS Code extension list — follow-up

CSS variables + one class toggle is my whole dark mode stack.

Interesting — I will have to try that.

CSS variables + one class toggle is my whole dark mode stack.

I still reach for Bootstrap when a client needs to maintain it afterwards.

I disagree slightly, but I can see where you are coming from.

Refactoring legacy CSS one component at a time is the only sane way.

:has() feels like cheating compared to what we used to do.

Could not agree more.

Container queries are great but I still add a media-query fallback.

Container queries are great but I still add a media-query fallback.

Refactoring legacy CSS one component at a time is the only sane way.

I disagree slightly, but I can see where you are coming from.

I still reach for Bootstrap when a client needs to maintain it afterwards.

I disagree slightly, but I can see where you are coming from.

:has() feels like cheating compared to what we used to do.

Container queries are great but I still add a media-query fallback.

I still reach for Bootstrap when a client needs to maintain it afterwards.

Container queries are great but I still add a media-query fallback.

That has been my experience as well.

I still reach for Bootstrap when a client needs to maintain it afterwards.

:has() feels like cheating compared to what we used to do.

I disagree slightly, but I can see where you are coming from.

CSS variables + one class toggle is my whole dark mode stack.

Good point, I had not thought of it that way.

That has been my experience as well.