I can imagine that getting confused with Guix (pronounced geeks)

I also recommend folks check out Dyson Sphere Program, I've sunk many hundreds of hours into it at this point

My favorite variant: Your secret is safe with my indifference.

For the first one, you should look into some z wave light switches; I have my house wired with them and then I setup triggers for things like "double tap this switch up to turn on the whole room" and "double tap this switch down to start a bedtime routine"

The unfortunate truth is that they do until they don't - Anyone I've spoken to in the service industry has basically said that they love the good busy nights and the rest is stressful. Nobody should have to worry that they might not get generous enough customers during their workday, else basically starve. What a horrible way to live.

It works fine for me, with a few small settings tweaks. I've probably logged ~70 of my ~310 playtime hours playing on Deck.

Of course it's mostly low settings, so it doesn't look as beautiful as it does running on my desktop via a 3080 at 1440p... but it looks good enough and runs well enough to be enjoyable on a handheld. I don't think I could enjoy an action-heavy game with the same performance, but for something turn-based that focuses more on the story, I'm having a blast.

That said, it sounds like that's the crux: I'm playing it in a portable fashion, on the Deck's screen directly, while it sounds like you're playing on an external monitor, with keyboard+mouse?

Nope. Price on the menu is the price I pay for a coffee. If you want more money, charge more money for the product.

I think it's supposed to be an option for ranked-choice or something.

Corrections:

1. They are not subdomains, they are just paths.

   A subdomain would be like programmer_humor.lemmy.world.

2. Communities exist on many instances, not just Lemmy.world

Tailwind is an unrelated project, that's just used by this one.

Basically, TailwindCSS is a combination of two things:

1. A huge set of "utility" CSS classes that apply consistent, basic styles, with tons of handy conventions for stuff like colors, shadows, border-radii, spacing - and it even lets you target them to hover state, active state, disabled state, users with prefers-color-scheme set to dark, etc.
2. A JIT-compiled system of creating one-off CSS by just writing the name of a not-yet-existent utility class.

The main benefits, I find, are mostly:

• Keeping your style controls directly present in the HTML, without needing to remember conventions or arbitrary "semantic" names for things.
• Consistency in convention. Need a color? There's a set (configurable) list of them. text-green-500 and you suddenly have green text with a middle-of-the-road luminosity. Need spacing? Use one of the padding or margin utilities, and you'll have consistent spacing based on a convention. py-4 and you know you get "level 4" padding without having to care what the exact pixel amount is. But! You know it's the same as everywhere else you've done py-4. No need to go fiddle with a stylesheet.

Tailwind focuses on coupling your styling to your HTML by using tiny, focused, glanceable utility classes (<div></div>) rather than by needing to create a ton of potentially-confusing "semantic" classes^[1]^ (<div></div>).

There are tons of classes in it, and I've found it to be super useful. Want to center something, horizontally and vertically? Here's how in Tailwind:

<div>
    <div>I'm centered!</div>
</div>

And if you need a one-off specific setup - something like display: grid; grid-template-columns: 30px 1fr 1fr 20px, you can do it with the JIT as such: `

If running php, I usually go with PHP-FPM and nginx, much faster than Apache in most cases

Ah, that honestly works fine in my book. It's a bit opaque, but it at least appears that 2xx04 acknowledges the existence of those licenses, which I'd imagine is good enough proof not to get in trouble somehow by forking it!