วีดีโอ

Thank you for sharing.

Bro you just forced me to subscribe to your channel. 🤩

I was actually needed this, but for a different reason. I finished my projects and was reassigned to another one, where other developer already worked on it. By myself I don't work with Tailwind at all, but on that project only Tailwind is used, so I has to adapt. But I know nothing about it naming system, so it look almost alien for me (of course some stuff cross with CSS with exact names, but still writing it on my own without suggestions is hard).

eww what that bratha

You don't even use any Ai copilot 😂.wow!

You don't even use any of this Ai copilot, You are a real developer. 😂

You don't even use any of this Ai copilot, You are a real developer. 😂

6:20 not clear too zoomed in.

I want tailwind prettier that auto splits long lines. I tried one but it's a but iffy

Just fell in love with tailwind after years of vanilla css

Excellent Extensions , I take the first 2. Tailwind doc is excellent, helps me to open doc just in vs code, and the tips for enabling string are just some magic things

Go 😂😂😂😂 i love go❤

Amazing video, earned a subscriber!

For me, the most important tailwind plugin after intelliSense is Headwind, which auto sorts your tailwind properties on save. Like prettier is for code, Headwind is for tailwind. I often have some very large classNames especially on a production project that will have responsive styling for screen sizes. After a while and without trying, your brain will accustom to the sorting and you will be able to read and edit tailwind styles much faster. Without even realizing it, I started to notice i could have very long classNames and when I wanted to edit something I would just go right to where the property was without having to read the whole classname. The other added benefit is that I don't think about where to add new properties anymore within a classname. I just always add it to the end and then it will be sorted on save. While you can customize the sorting orders I have not messed with it at all and still use the default sorting order. TBH, I haven't looked into much detail on how it sorts or what it prioritizes by default. Like I said, with time it just became natural where to look for things without any thought or effort into it.

Golang called, they want their if (err) return [err, null]; back. Jokes aside, if golang had a "throw" to populate those it would be awesome but guess JS just got the hannah montana package (best of both worlds).

Pretty awesome recommendations

Thank you

another W Video 🙏🙏

another tip i got for the Community 🐥 When using selectors with 1px for Example "h-[1px]" or "border-[1px]". In most cases, there are shorter ways to write this. For these Examples: "h-px" and just "border". ✌️

Oh great, thats just what i needed ⚡

Thanks sir

First to comment 😅

And would you believe other languages already got over this? 😅

Try/catch is by far superior: it allows to focus on a normal flow and not to react to every possible error at every possible level. Imagine having a chain of 10-15 nested calls and error checking at each level just because at the deepest level something fails. This is when the code gets insane. And the example inn the beginning of the video with a separate try/catch to every call only shows a misunderstanding of the concept. Yes, I know that nothing is given for free: the try/catch mechanism is quite complex and eats a lot of resources. But it makes the code by far cleaner when used properly.

i love it ❤

the [...] = operation is very computationally expensive if one knows how js works internally. I'd opt for something else as Effect for example.

ShadCN's carousel is built on top of embla carousel. So shadcn DOES support something like what was shown in the second example.

How do you create the zoom effect? Are there any OBS plugins or other tools for it?

Stop saying "Bad Code" since it still works, just say "Old Code"

So, basically copying Go's error handling?

more bloat into the language, just stop.....

Awesome bro thanks👍

Looking forward to seeing this feature being released. Just awesome 🎉

nice video only i get crazy of so much stupid zooming so very annoying, would not watch again if this is going to be standaard

Copied from golang :)

I like the nesting. It's easier to read.

Reminds me swift

please, if possible make a video or a short on how you are editing your video with this zoom in to focus effects

So, uh, what was wrong with this? let res[2] = call(); if ( res[0] ) return res[0]; res = call2(res[1]); if ( res[0] ) return res[0]; ...

So instead of adding isLoading={true} to any of the button variants and having that handled automatically, you have to use a separate LoadingButton component? Not a fan of that.

Thank you.

Bro, we know you are a handsome human being, but I am sure people prefer to see more code and less faces. Thank you.

TBH I prefer when all of those 75 inputs live inside a single Input class that is configurable via props. That's how larger component libraries like Mantine or MUI do it, and in terms of code maintainability, it's much easier to deal with. Nonetheless, very cool that this exists!

That's the reason why I use a Result object instead, but basically this new operator would do the same. Pretty neat

What a book❤❤

The “await-to-js” npm package does this. Or you can simply create your own version.

might-fail is a package that does this for now, quite well

Your content is fire bro

Isn't this part of typescript?

inspired by golang