Hacker News new | ask | show | jobs
by DidYaWipe 596 days ago
Here are a few threads from the forums; there are probably more. The first seems the most extensive. To be fair, I'm not sure if there are employee responses in there or just eager apologists ignoring evidence and blaming other users for the defective behavior:

https://forum.affinity.serif.com/index.php?/topic/53609-merg...

https://forum.affinity.serif.com/index.php?/topic/185759-sto...

https://forum.affinity.serif.com/index.php?/topic/166381-see...

1 comments

The first thread is large, for sure, but is it relevant? Why do all of these have to do with pixel art, which is something you probably should do in a pixel art editor (Aseprite[0] is great, cheap and deserves your support)?

If this is indeed an issue overall it would be very ironic because the Affinity suite of products are (as far as I understand) way more focused on and enable a non-destructive workflow than Photoshop and its related products. I think it's a big "if", though, no offense intended.

0 - https://dacap.itch.io/aseprite

"Pixel art?" They all have to do with photo (bitmap, rather than vector) editing.

I sincerely have no idea what you're talking about.

2 of the 3 threads you posted are specifically related to pixel art.

The first linked thread is by a person who is doing pixel art. “I'm working on pixel art (very small-resolution bitmaps)”

The second thread you linked is also by a person doing pixel art. “I work on pixel art a lot”

This doesn’t take away from the fact that there’s a blurring issue happening that Affinity don’t seem to be able/willing to solve as of yet, just making it clear that you linked to two threads by people doing small bitmapped pixel art, then denied they had anything to do with it.

<crickets>