Great explanation, thanks

Can you elaborate? I googled the right hand rule, but I’m not seeing how it applies to screws.

Ah, there it is. I was focused on the wrong thing

What’s different?

MVP

I know the feeling. A few months ago I randomly got a video call from my boss. Both he and the owner of the company were in the line. They let me know that they unfortunately had to let go of almost everyone on the dev team. Some funding had fell through (gotta love startups). Fortunately, I got to keep my job that day, but I can’t shake the feeling that another layoff is right around the corner.

Are these not valid questions? Serious question, don’t mean to offend. I got asked the same types of questions before my doctor agreed to do my vasectomy.

How can you know? According to the documentary, 2 girls 1 cup, it’s very tolerable for humans.

I think I got it.

The right side is showing what percentage of games can be played at each level. Platinum is flawless, and borked is… borked. The percentages below that show that 84% of games are super playable, 95% if you’re willing to settle for silver.

The outside ring is the one that shows these percentages.

I’m still unsure of the center rings though.

deleted by creator

I’m actually pretty salty that they ported over all the good titles. It was kind of a slap in the face to everyone that invested in a wii u. It’s the only console to not get a unique zelda release (you can’t convince me that they didn’t delay breath of the wild specifically so they could do a dual release). Then most of the other games were low quality because they didn’t want to waste money on the few people that did buy a wii u (Smash bros didn’t have anything resembling an adventure mode). Then, to top it off, they ported all of the good games over to switch anyways.

deleted by creator

Is there a separate conversion chart for every food out there? Seems confusing.

How do you convert cups to weight accurately when a cup of one thing might weigh more than a cup of a different thing?

I feel like im slowly losing my ability to program between copilot, phind, and chatgpt…

I am not serious, lol. Can I ask how you think we as a society should handle these individuals? I know you said that they “should get the short end of the stick”. Does that mean execution? Life-imprisonment?

How can you say all that when you don’t even know what the victim was wearing?

deleted by creator

I guess it comes down to preference. I personally don’t mind scrolling down a little bit to see my styles if it means the structure of the component is cleaner. I’ve found that I can iterate faster that way. If things get too unwieldy, that usually indicates to me that I should extract something out into a separate component.

About point 3. At least in svelte, you don’t have to worry about having unique class names. The styles are scoped to the component. Meaning that the CSS you write in one component doesn’t affect any other components (unless you explicitly want it to). So you can reuse class names on multiple components and they won’t interfere with each other. for small components, I’ll often not even use class names if I can get away with it. I’ll just use element selectors.

You can also get this functionality with React and Vue using CSS modules.

I can see why one would prefer Tailwind over traditional CSS though. Especially if you’re writing straight HTML/CSS, or if your chosen framework doesn’t support scoping styles to your component.

IMO, scoped styling removes Tailwind’s usefulness.

I’ll use Svelte as an example. In Svelte, you can just put a style tag at the bottom of your component, and everything you put in there is automatically scoped to it. I’m not hunting through dozens a CSS files trying to find where a class was overridden and adding !important everywhere. Using vanilla CSS allows me to keep my markup clean and concise so I can better see the actual structure of each component without dozens of CSS class names cluttering everything up.

Sure, you can write your own class in Tailwind using the @apply directive, but why not just add a global CSS class? That’s essentially what you’re doing anyways. And now you don’t have to hunt through multiple layers of abstraction to figure out what styles are actually being applied.

In my experience, Tailwind was good as long as I didn’t try to do anything too interesting. What ended up happening in my project was that I would use Tailwind classes for basic styling, then break into vanilla CSS whenever Tailwind wasn’t sufficient. And that meant I was looking in multiple places to see what styling was affecting my component… which kinda defeated the purpose of using Tailwind.

Personally, I also just found Tailwind harder to read. I prefer to read code vertically rather than horizontally.