> I don’t really get pre processor vs post processor, it’s a build step to run at some point before I deploy with either tool that will produce some css files.

> I don’t really get pre processor vs post processor, it’s a build step to run at some point before I deploy with either tool that will produce some css files. Not quite the same. If it's only a preprocessor, the tool is only dependent on your styling code. A post-processor needs the whole application. It's a lot easier to add or remove a pre-processor from your development process, and for those that want to consume your styles it is a lot nicer when you don't have to adopt their tooling as well. E.g, I can create a "utility class library" in SASS, generate the CSS and let people just import that directly into their web pages. Is that possible to do with tailwind?