IMO the killer feature of tailwind is that it lives alongside your React components so you keep things DRY, and you get a design system with type and spacing scales out of the box. It’s a form of constraint that helps create structure. But I think that makes it a victim of its own success. The tailwind spec becomes ever more complicated the more native CSS features it tries to include. I’ve seen tailwind incantations go way beyond editor wrap line
I still like it though. it’s one of those abstractions that actually helped me learn. I would go to the tailwind doc pages and see the underlying css of any class.
There were some other frameworks I got excited about: vanilla extract and stitches, both made by some really talented people. I wonder why those never quite got the same traction…
In my opinion, AI art is best when it laughs at itself in a meme context. For e.g. the recent General Grievous Pawn Stars video, or the Indian Hulku-re meme. When it tries to take itself too seriously to approximate reality, then it becomes icky.
How can vintage models be contamination free if a newspaper clipping with “general relativity” accidentally slipped through into the training data? I don’t see such a guarantee described in the methodology
In contrast, I asked it about the lumeniferous aether and the Michelson-Morley experiment (which was late 19th C) and it said the aether was not disproved by the experiment (even though special relativity was like 1905 or something).
So definitely the event horizon of the model’s knowledge is a bit porous/nonspecific in either direction.
I still like it though. it’s one of those abstractions that actually helped me learn. I would go to the tailwind doc pages and see the underlying css of any class.
There were some other frameworks I got excited about: vanilla extract and stitches, both made by some really talented people. I wonder why those never quite got the same traction…
reply