Комментарии:
woah im early
Ответитьv4 is huge, game-changing!!
ОтветитьI love how the config file for Tailwind is now a CSS file. Seems like the complexity of the JavaScript-based config file was a bridge to get us to this simpler config.
ОтветитьYeah, imma stick to modern vanilla CSS and its APIs + useful patterns. No need for injecting even more bloat and unnecessary complexity.
ОтветитьThis podcast would like go totally next level if we just had visuals of what you are speaking of at the very least the page you are browsing, or docs, or even if it’s just when you are talking syntax no pun intended lol.
Because it’s not as graspable unless I have previously read it. And the whole point of a podcast is to be newsworthy and informative
Tailwind 4 is fantastic
Ответитьplain css FTW ... with all features including variables, queries etc
ОтветитьI still can't get my head around tailwind. It's inline CSS with extra steps... Maybe if you never learned CSS before, it might be helpful - for me it just makes everything more messy.
Ответитьfocusing on scotts camera and seeing he is not in the room is hilarious 🤣
Ответитьno code?
ОтветитьIT would be Sooo invaluable to display the code feature while explaining it. thank you for sharing.
ОтветитьTailwind 4 is awesome. However, I have to stick with v3 for a while (our application is stable). I'm still not convinced about custom variants with var (e.g.: bg-(--brand-color) vs bg-brand-color); perhaps there's a way to still use the old syntax.
I will look into it later.
have they fixed media queries? as in like chaining a list, rather than prefixing every rule? ie changing this: `md:text-black md-flex-row md:bg-orange`
ОтветитьTailwind 4 sucks, it breaks with older browsers, and I am not taking IE7. It’s an absolute disaster in production. Make sure of your SaaS user config, as if you blindly upgrade, your risk having a bunch of clients being pissed of.
ОтветитьBefore posting how amazing Tailwind 4 is in the comments; go and try use it, try to migrate.
You'll find a lot of things I and the some of the community do not like about the v4 changes; in theory it's nice to have a CSS only config, but there are a lot of annoyances it brings too. Need to stick to v3 for the foreseeable, maybe they'll iron out some DX problems over future releases.
Rückenwind 4 ist da!
Ответитьwait scott doesn't hate tailwind??
ОтветитьWes, where can we get that hoody?
Ответитьfml - i dont know whats worse, learning css functions or memorizing more tailwind slop.
ОтветитьSo tailwind4 adds modern css that has been around for 3+ years? Probably the same time frame it takes for anyone to update the design and layout of a large website created with tailwind.
ОтветитьGreat episode!
Loved seeing Scott's background unblurred for once 🤣
Poor Scott. Nobody should have to use Tailwind.
As a contractor I keep being forced to use it and it just has zero appeal.
Instead of just knowing CSS now you have to know an entire abstraction layer built on top of it.
I spent most of my time trying to translate the CSS I want it to the equivalent Tailwind class. 🤦♂
I am loving TW4 so far
ОтветитьTailwind becoming Unocss lol
ОтветитьTailwind obscures browser compatibility issues until you hit them hard… And TW4 has too high browser targets.
ОтветитьI love Tailwind ❤❤❤
Ответить