The single reason I do not use Tailwind CSS—It's inefficient for prototyping

At this week's ColumbusJS Meetup where Nathan Lieberman presented on Tailwind CSS, I once again complained about the fact that I cannot use Tailwind CSS to prototype in the browser without context switching back to an editor. It is probably the single reason I do not use Tailwind CSS.

To explain the problem again, the work flow for using Tailwind CSS is inefficient:

Add/remove/change CSS class in IDE or editor guessing what would work.

Wait for hot reload.

Change to a browser to visually test.

Change back to IDE or editor to refine

Wait for hot reload.

Change to a browser to visually test.

Repeat

Where...

https://nokoto.org/user/3/posts/1011