There are some pretty big key differences though. Livewire is pure ajax (at least for now, may change in the future, a rewrite is in the works), Hotwire is mostly websockets. Livewire does DOM diffing in the frontend, Hotwire does it server side (sorta? didn't dig a ton but that's my understanding). Performance characteristics are pretty wildly different depending on the usecase.
The DC National Guard, unique among all other guards, is under the command of the President. A state governor can call up that state's Guard, but the government of D.C. cannot.
I know the Tailwind guys are working on a project called Headless UI[1]. It's a component library without the styling. There is also Tailwind UI[2], which is more like Bootstrap. Both are official Tailwind projects.
My developer co-workers and I have talked about teaching our designers how to code with Tailwind. The designers have no experience with writing code, but I still think its a good idea to start with Tailwind because you'll use many of the best practices and avoid a lot of the historic madness in the CSS world.
It's like buy Ikea furniture and assembling it vs. having your own woodworking shop to handcraft furniture with precise requirements. These frameworks have made me lazy. I think CSS design is pretty much exactly the same as any craftsmanship job - there is so much pleasure from building it from the ground up. No, I still get the knots in the wood out by using reset.css.
Also, I try to not use class selectors as much as possible. HTML looks sterile and spartan with only a handful of span tags or id tags for very specialized targetted changes.
I can see why people use frameworks - its fast and quick. But you lose personality in the outcome.
The case between Apple and Epic Games is about the app store on iOS. Epic can sell games without having to give Apple 30% on Mac OS. I doubt the investors is on board boycotting Apple as a whole.
