Grunt is still relevant isn't it?.

Is today the day I finally watch these talks by @paul_irish that I added to my "watch later" list nearly 10 years ago?

Generate videos in just a few seconds. Try Grok Imagine, free for a limited time.

Now, I feel politically or ethically opposed to it. Feels like a bad relationship. I'm gonna log off for at least a few months. Love you all.

Regardless of whether Twitter survives this current shit show, I can't see it ever being the place I remember. It was once exciting, I learnt heaps here and connected with a people who still mean a lot to me.

You can configure classAttributes: It's not looking promising, but parsing a type and applying intellisense that way would be an awesome feature.

P.S @CoreyGinnivan is really great.

It's not that Tailwind will teach you nothing about CSS or that CSS will suddenly teach you everything about browser specifications. We've got to stop saying both of these things and show people how they relate.

I just have a problem with the idea that Tailwind will teach you CSS really well. Because it's only a starting point and I think if you can also write CSS, you'll have more insight into how and why it works browsers work the way they do.

If CSS is not going to teach you everything, Tailwind will only make it a little harder. I know diligent people will follow the thread and learn the stuff they need. I have no problem with Tailwind being the starting point.

It's similar with Tailwind. You might not even think about supports because it's not part of the standard Tailwind API. You might only read the Tailwind docs and miss out on all the really cool stuff MDN can teach you about related fundamental CSS concepts.

Abstractions can also be distractions that make it harder to learn underlying concepts. Learning native JS is not going to directly teach you about the event loop. It might be hard to see when caught up thinking about the React lifecycle/hooks.

This is a fair point! CSS itself is a layer of abstraction that controls part of the browser rendering process. So 100% you're going to have to do extra work depending on how deeply you want to get into underlying concepts.

P.S I still love you @simonswiss.

We need to kill the dogma and have much more balanced and honest discourse from both people that love Tailwind and those that hate it. Sometimes it IS a bloody useful abstraction, but it DOSEN'T cover every CSS property and it will NOT teach you many important concepts.

To write custom CSS you typically have to do this in a separate file. Tailwind kinda exists simply so that you don't have to do this. In fact modern devs see this as such an anti-pattern they add far more complexity to avoid it than the cost of a CSS file.

With a useEffect hook you might interact with the DOM or an API or something non React. You might import libraries or custom native code too. But with Tailwind you don't do this in the same context. Classnames are there with the React code or whatever you're using.

But I feel like it's more widely accepted that React developers will eventually need to learn JavaScript fundamentals and the path is easier because you do this in the same context.

I know a lot of developers who are good at React but some of them could not manually attach an event listener to a DOM element to save their life. And beyond the built-in DOM methods, just like Tailwind, there are a bunch of concepts in JavaScript that React doesn't teach you.

I just don't think learning a higher level abstractions will ever teach you the fundamentals. It's ok to use it, but you will need to do more if you really want to understand what it is doing under-the-hood.