Another one comes, 🎉, really love your content, love from Kenya

as always good stuff Josh !!

Great content Josh. Tks to share.

god tailwind is a gift that keeps on giving

Josh you explain very well. Liked & Subscribed

I knew about and used the group classes but didn't know there was one for peers. Thats awesome.

Ok, help me understand why this is such a big thing. With pure CSS you also don't need JS for achieving this, or am i missing something? With input[type='submit']:checked + div > .classname I can also select the div on the same level and go one deeper. Was this only a thing which was not possible with tailwind before?

Something tells me we are going to have a tialwind state manager. Let's see.

Not only did Josh get a Mac, he also started using Arc! I'm also a very big fan of Arc, so I welcome the change 😆

looks awesome, is that signal a special keyword? Wonder what its like to define a signal, and inbetween a nested child, define another signal. Would the most nested child be able to access both signals?

This could be very powerful with React Server Components to give some interactivity that we only think could come from js rn without js and removing the need for 'use client'... nice. Can't wait for this to become standard. Thanks for the info!

Hi, Josh, I hope you already know about problems with self closing tags from Prime's and Theo's videos. Love your videos

your the best thanks ... 😂

Josh moved to Arc too 👀, i can't wait for it to come to windows

Started using TailwindCSS back in 2020, currently switching to StyleX. Tailwind made bigger projects real mess to work on. For Presentational websites, yes, it's great and easy to use.

It's helpful

one small note: are not on the same level, because using the closing tag for a div causes this to happen: e.g.: Hi! is equivalent to hi! therefore: is: this is because browser ignore self closing tags on some elements for some reason that has to do with XHTML and XML and W3C stuff.

Using group has is a super clean way tho. I'd use group-has before using this.

To be fair all this stuff is possible with plain css afaik so the “no js” praise seems a bit much to me, it’s just a way for tailwind to now have any drawbacks compared to regular css

What browser do u use?

Whats the browser youbare using

Hi, as i am watching i am really curious about how multiple signals are handled.. let's say you have : Component-Level-1 triggering a signal Signal-A Component-Level-3 trigerring a signal Signal-B Component-Level-4 trying to listen to signal B Component-Level-7 trying to listen to signal A By just specifying "signal", which signal the Component-level-/ will peek? A or B?

I love the tailwind ecosystem, and see the value in this too as I explored it as a video idea as well. But personally I dont like adding on plugins like this to tailwind, the only one I ever use is tailwind-animate. I like my tailwind to be as compatible as possible so if people copy my code snippets, or If I copy from another project, it should just work with stock tailwind set up, and not have another source of documentation to look at. It seems like we get enough of this functionality with groups as is. Projects like this have great value for people that see their uses though and it keeps pushing the tailwind team too to focus on DX.

Now CascadinG stylesheets are inside classes itself instead of css files/style tags

Thank god, I thought tailwind was entering the JS land with signals.

which browser are u using?

What if i have an input as child and I want to style its parent based on input peer?

if we build the react project, doesn't it convert to html, css and javascript? I must be missing something, else Tailwind Signals would be supported on all browsers.

So alpinejs but in tailwind?

How about have more signals in same tree ?

off-topic question: what browser is that in the video?

Yes, I program in CSS programming language, babe.

Now this is called over engineering

Wouldn't this make it hard to debug in complex applications?

why make the group/peer something ground breaking, it's a basic css feature

"P'suedo classes" for the win!

There's nothing groundbreaking here. Tailwind is just solving a problem it itself created. Plain CSS can do all this in a far cleaner way.

I am already using groups, i do not see so much the need of passing it from child to parents, as in react is a nice one way street which gives good structure.

Looks like the word "signal" is all the rage in web dev these days...

why is excalidraw so laggy for me?

You keep saying the classname changes based on the signal, but surely that's not what is happening?

I’ll wait

Thats cool, but man is that going to get ugly haha. Not for me, but its cool!

Game changer!

I pitched Tailwind to my team at work, hopefully we can hop off bootstrap soon😭

Since when is he using Mac OS?

I'd rather use CSS to style active states for readability

I generally like Tailwind, but dislike this idea a lot. Once you need significant amounts of logic for applying css classes, you might as well use js - especially if you're using a reactive framework like React or Solid.

Hi

Ur cooked 😭

Finally switched to mac?🤓

People trying so hard to not write css. Do you guys realize that the tailwind.css file is global and you create a shit ton of singletons, that massively bloat your resulting tailwind.css file? I do love tailwind, but this arbitrary selector stuff has to stop.

This is a terrible idea and a maintainability nightmare.

Peers.... wtf :D

I would usually say: write css you bums. Tailwind is pretty cool for AI generated markup though at least

even Tailwind is using the signal concept now. But React 😐

I have never understood why people use Tailwind and this makes me understand it even less.

My eyes hurt by just looking at it. Don't use Tailwind, and those "states" won't work in real projects.

It hurts me that this video assumes you use react if you use tailwind 🤦‍♂

This looks horrid, and how is this any different to just adding a generic css selector? input:invalid + div {} ??? The abstraction that tailwind promotes blows my mind, just learn javascript and css and you won't need things like tailwind at all

Frameworks and libraries are getting worse everyday

horrible naming. should've used another word instead of 'signal', an already confusing term