tuna

LMAO, yeah this one didnt seem to hit did it

fish. I think it has most things i want out of the box, so it should be simpler and snappier than my zsh setup. it's just that zsh hasnt bothered me enough to try it yet.

also nushell, im interested in the idea of manipulating structured data instead of unstructured text

And make sure the time is synced to the cloud so they need internet connection, and so the player can't be sneaky and reload the game to reset the timer if they pressed x too many times

This reminds me of my ex gf 😅 not only does she enjoy "kid" shows and movies, but HER NAME IS ANDY TOO. That image would definitely dealt some damage. For us though we broke off on good terms. Right person, wrong time, wrong place :(

Happy to participate!

The one thing I wasn't super sure on was the undo timer... was it really 30 seconds 😅? I thought it was 5-15s, but i didnt really time it. And I'll be honest, I missed it maybe 3 times, so not much.

Besides just increasing the delay, there's 2 other thoughts:

• A bigger target takes less time to hit (tho making it bigger might bother some, as it obstructs the canvas)
• Two times I missed were bc I failed to notice my mistake. Maybe some extra visual feedback when you place a pixel could help. For example: when the void made it to my art, I accidentally made a dark gray become black, so it was harder to notice the color change. i was too busy focusing where to place the next pixel

Overall if you feel that the undo time was fine as it was I could easily respect that decision :)

I think I agree on the cooldowns. Often times I wanted to step away and let the pixels accumulate, but it's hard to resist when you realize you'd be missing out on double or triple the amount of pixels you could be placing. If the goal was to reward the player for actively placing pixels, all I can say is it didn't feel very rewarding.

I kinda disagree about the integer scaling. 1x to 2x zoom is a very big shift without any in-between. It would also feel strange on pinch-to-zoom on mobile without in-between. I think instead it could snap to an integer scaling, or have a zoom slider that works to integer scaling. Overall though I agree, having a way to snap into integer scaling makes the pixel art look better

On mobile I kept opening the whois pixel by accident when dragging. I often tap and hold to initiate a drag because I'm still looking at the art, but when i drag away and let go, it opens the whois thing. I think if you drag a certain screen-space distance away it should cancel the whois pixel lookup.

The heatmap I found too hard to tell where recent pixels were placed. I think at 100% opacity the "cold" pixels should be dark blue instead of their actual color.

A couple times I placed a dot, realized I actually didn't want it there and ran out of time to undo, which felt bad having to wait 30s. I wish it was a bit longer.

When you try to place a pixel a few milliseconds too early I feel like it should queue it and wait the few milliseconds for you.

I'm not super sure on the canvas having transparency. Most people treated the canvas as white, not transparent. If you wanted a white-on-white drawing, people will just make an outline.

Maybe a concept worth testing: if you place a pixel next to your own pixels, you get a (slightly) reduced cooldown, that way you get an extra boost when completing your art. (At the same time, I think there is beauty in the canvas being as simple as possible:)

1. RIP Apollo
2. I almost didn't join lemmy because the first time you sign up in the fediverse it feels like a big deal. What got me to actually follow through was to impulsively join a silly instance (RIP iusearchlinux.fyi)

i tried to fill in the blåhaj but i ran out of time D:

I noticed it and placed a few pixels :D

Here's one on the claw

You might be okay with this:

macro_rules! span {
    ($line:expr, $column:expr) => {
        Span {
            line: $line,
            column: $column,
            file_path: None,
        }
    };
    ($line:expr, $column:expr, $file_path:literal) => {
        Span {
            line: $line,
            column: $column,
            file_path: Some($file_path.to_string()),
        }
    };
    ($line:expr, $column:expr, $file_path:expr) => {
        Span {
            line: $line,
            column: $column,
            file_path: $file_path,
        }
    };
}

Playground

However, sometimes I don't want to pass in the file path directly but through a variable that is Option<String>.

Essentially I took this to mean str literals will be auto wrapped in Some, but anything else is expected to be Option<String>

Another optimization:

• The first index of each index array can be filled by a function. For 257x257 that would remove 8,487,169 checks out of... 2,164,392,321. Not much, but it's basically a free optimization, so might as well!