[harles]

> Windows has caused us a lot of issues with Upscayl

I’d turn that around. Sounds like Upscayl has caused a lot of issues for Windows users. Not developing on and doing little testing on Windows sure sounds like the problem to me.

[indymike]

First, I love Upscayl. Just used it to make about a decade of early lower resolution digital family photos 90s and early 00s printable and beautiful on HDPI screens. It's fantastic software.

> Not developing on and doing little testing on Windows sure sounds like the problem to me.

Most open source developers are not going to switch to "developing on" Windows because of posts like this. Nor should they. Upscayl is on GitHub and would probably appreciate some testing and fixing on Windows.

As a developer, I don't use Windows at all. When I make cross platform software, dealing with MS-DOS anachronisms isn't interesting or fun. For paid work, yeah, OK I'll do it. But for free stuff, I can see where a developer might not want to put a lot of effort there and focus on the interesting part of their project.

[Dalewyn]

>But for free stuff, I can see where a developer might not want to put a lot of effort there and focus on the interesting part of their project.

That's perfectly fine so long as one doesn't claim to be cross-platform (or supports Windows).

[NayamAmarshe]

but it is cross-platform and supports Windows.

There might be Windows specific bugs but those are fixed as soon as the community gives feedback.

[NayamAmarshe]

I'm just saying how Windows increases the development time compared to Linux and Mac when using technologies that utilize Mac/Linux standards.

Being a cross platform application, Windows gets the same stack but is the cause of more unnecessary issues.

It is true that we don't have enough testing for Windows but that's because I do not have a Windows machine and Upscayl won't work in a VM so I have to rely on community feedback most of the time.