3 ms·

Windows has caused us a lot of issues with Upscayl (https://upscayl.org https://upscayl.org). I personally do not use Windows but most of our errors are report

Windows has caused us a lot of issues with Upscayl (https://upscayl.org https://upscayl.org). I personally do not use Windows but most of our errors are reported by Windows users where sometimes path parsing is a problem or the drivers mess up vulkan configuration. The fact that node takes a different approach to windows paths and sometimes the need to store these paths in storage and re-use them in external spawned processes makes it difficult to work with Windows' different and not so ideal path standards.

harles 2y ago
> 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 2y ago
  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 2y ago
    >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 2y ago
      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 2y ago
  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.
jonathanlydall 2y ago
Our desktop product built using Electron and .NET runs cross platform. Originally it was on Windows only and I personally did the work required to make it work cross platform once .NET Core became mature enough, so I’m very familiar with the path separator challenges. It was a bit of a pain, but not a huge deal. The trick was to just use forward slashes all the time, except for display or storing an absolute path. Windows doesn’t seem to care when you use forward slashes for everything even if looks wrong. Admittedly the Node code dealing with paths is limited as most of the heavy work in our app is done in a .NET background agent, but there are things like file selection dialogues and config loading that is in the Node part. Based on the fact I can’t remember exactly what I did for paths in Node leads me to believe it was pretty much a non-issue, I probably used forward slashes and it just worked. It took a lot more work for the .NET aspect where we’re doing a lot more stuff on the file system, I had to find and replace most path usages with a utility function to convert the separators appropriately.
lm411 2y ago
I'd never heard of Upscayl before. Very impressed! Works great on my Mac.
- NayamAmarshe 2y ago
  Thank you! Glad you like it :D

harles 2y ago

> 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 2y ago
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 2y ago
  >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 2y ago
    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 2y ago
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.

jonathanlydall 2y ago

Our desktop product built using Electron and .NET runs cross platform. Originally it was on Windows only and I personally did the work required to make it work cross platform once .NET Core became mature enough, so I’m very familiar with the path separator challenges. It was a bit of a pain, but not a huge deal. The trick was to just use forward slashes all the time, except for display or storing an absolute path. Windows doesn’t seem to care when you use forward slashes for everything even if looks wrong. Admittedly the Node code dealing with paths is limited as most of the heavy work in our app is done in a .NET background agent, but there are things like file selection dialogues and config loading that is in the Node part. Based on the fact I can’t remember exactly what I did for paths in Node leads me to believe it was pretty much a non-issue, I probably used forward slashes and it just worked. It took a lot more work for the .NET aspect where we’re doing a lot more stuff on the file system, I had to find and replace most path usages with a utility function to convert the separators appropriately.

lm411 2y ago

I'd never heard of Upscayl before. Very impressed! Works great on my Mac.

NayamAmarshe 2y ago
Thank you! Glad you like it :D