It's an interesting approach, but does it really solve the problems atomic/functional css have asude from purging/unused styles? I always felt like the most us

It's an interesting approach, but does it really solve the problems atomic/functional css have asude from purging/unused styles? I always felt like the most useful thing tailwind actually brings is the preset based style system, as a dev u don't need to remember if the styleguide calls for 6 or 8 pixel space, it's just "m" to me and i can apply styles without worrying too much about design details. If this approach compiles the atomic classes depending on arbitrary numbers, have i gained anything aside using the "class" instead of the "style" property? (aside specificity of course)