I'm quite deep into react, angular, angularJS on the frontend spectrum. Still my first reaction was: "JIT? CSS? Wth?"
My reflecting alter ego of course tells me this is quite probably a great achievement. And I'll read into this matter professionally, probably use it where appropriate. Still I think a world where JIT is needed to process a non-turing complete layout language (which I know has turned into a horrible mess of sibling-eating lovecraftian, hieronymus-bosch-y amalgamation of CSS and javascript) is doomed to fail.
The JIT isn't for compiling CSS itself, but for scanning for classes tailwind supports. Essentially it scans your code (HTML/JSX) for those classes, and only generates an output CSS file with those classes.
My reflecting alter ego of course tells me this is quite probably a great achievement. And I'll read into this matter professionally, probably use it where appropriate. Still I think a world where JIT is needed to process a non-turing complete layout language (which I know has turned into a horrible mess of sibling-eating lovecraftian, hieronymus-bosch-y amalgamation of CSS and javascript) is doomed to fail.
This felt good (note the past tense).