Jonathan Pollak

Thank you. This is great

It might be easier to flatten them out. ```css @media (max-width: 400px) { @media (max-width: 300px) { /* ... */ } } ``` Is exactly the same as ```css @media...

With atomic CSS, this approach will fail in quite a few, much more basic cases than the ones mentioned above, and there has been rather extensive discussion of the issue...

Thank @madou Duplication would indeed work in this naïve example, but in other cases, could also cause unexpected inconsistencies, because it still alters the cascade (definitions bubble up - `.b`...

Another point is that size-wise, duplication doesn't save the JS boilerplate, it just defers it to a later time. You'd need it anyway to move the content of the different...

It's a lot more straightforward with a single stylesheet (extracted or in `head`). What you'd basically do is figure out the order ruleset types (e.g., lvfha, media queries, etc.) should...

Feature queries (`@supports` blocks) also come to mind in the same way as media queries, but I'm sure there are other edge cases I'm just not thinking about right now....

I believe there are other cases where this could fail. Reliance on the cascade is indeed significantly decreased with atomic css, but it is not completely gone. For instance, the...

I'm trying to understand if the use case requested by @skellyb (`{ fontSize: ['32px', '8vw'] }` --> `.a { font-size: 32px; font-size: 8vw; }`) is supported by #145, into which...

Yes! npm got back to me yesterday that they have contacted the owners of `@fela` and have given them until the 9th to respond. It seems inactive, and if there...