4 ms·
Could you explain the performance problem ? I understand how you could get to the other claims, even if i disagree. But i sincerely do not understand the perfo
by di4na 3y ago
Could you explain the performance problem ? I understand how you could get to the other claims, even if i disagree.
But i sincerely do not understand the performance one. If anything tailwind approach is mostly really good for performance, as rendering utility class directly on the element is still the fastest, by far, technique.
The only slight call here could be shadow dom scoped but that necessitate declarative shadow dom and create a lot of problem for performance until we get a fetch maps equivalent to import maps.
What have I missed?
- danielvaughn 3y agoYou haven't missed anything. I swear, every time I read a thread on here about Tailwind I feel like I'm taking crazy pills. So far I've heard: 1. Tailwind allows you to not learn CSS (not even remotely true) 2. Tailwind is hard to move away from (what?!) 3. Tailwind has performance issues (lol)
- ethanbond 3y agosomething something 3rd party dependencies bad for (?) reasons