Yes, you can check off on your list that you no longer have any .S files. But did you actually gain anything?
> Most C libraries do too much.
> They come with all sorts of predesigned components like functions and structs that might help you move quickly at first, but cause more pain than they cure when it comes time to make your program stand out with custom behavior.
> Tailwind C is different.
> Instead of opinionated predesigned components, Tailwind provides low-level utility macros that let you build completely custom functionality:
void main() {
BEGIN_TAILWINDC
MOV(RAX, 4);
MOV(RDI, 1);
MOV(RSI, "Hello world!\n");
MOV(RDX, 13);
INTERRUPT(128);
END_TAILWINDC
}
And then every Hacker News discussion of Tailwind C would inevitably include a link to their "Why using Tailwind C is definitely not just as bad as writing inline assembler" documentation page.Ooh, and then the creator of Tailwind C would start selling the Tailwind C Library, with like an implementation of memcpy that you just cut-and-paste into your program every time you need to copy memory.
The leap between vanilla css and tailwind is not large at all.
Assembly: raw html and css C: A framework like Tailwind Python: Components, like TaildwindUI or any of the React components I’ve seen
I think that’s not a bad analogy.
Caveat: not a UI developer, I’ve mostly done backend work And DevOps for quite some time.
It's an interesting concept.
It’s way too much effort for me to want to mess with, and then you have to repeat the same things for every site you make.
See how dumb that sounds?