As with recent platform updates, we are now fully adaptable to 32-bit and 64-bit operating systems. Theoretically, there should no longer be a need to offer only 32-bit versions of apps with compatibility in mind. Is it time to offer the 64-bit version of the application to all users who prefer it in their platform settings? (if there is one)
Since some applications are not updated as frequently, can we provide a feature for users who have chosen the preferred 64-bit application to convert the legacy 32-bit version of the application to the 64-bit version of the application? (and vice versa)
https://github.com/sabrogden/Ditto/releases/download/3.24.246.0/DittoPor...
For many apps, the 64-bit version doesn't offer anything over the 32-bit version. Including the 64-bit version in a dual architecture package doubles the download size, bandwidth, and storage size. Making separate 32-bit and 64-bit versions of apps would add a lot to maintenance and build time. Plus, the PA.c Platform doesn't yet automatically close 64-bit apps, though I'm working on that for release in the semi-near future.
Please remember that at present, I'm basically the only one maintaining all ~1,000 app packages available in the app store.
Sometimes, the impossible can become possible, if you're awesome!
Is there a possibility to write some scripts for each application to build the portable version packages automatically?
I feel that it's not realistic to rely solely on you to manually build more and more applications one by one. Can we consider some degree of automation?
Also, can we consider hosting the installation package on platforms like SourceForge/GitHub that have a CDN?
This may alleviate the pressure on the server and solve certain network problems. (For example, errors or slow speed, etc.)
No M$! - Open your source! Make people's lives easier!
We already host all of our open source apps on Sourceforge. Our dedicated servers are only for our freeware releases. When there are speed issues it is usually Sourceforge that is the problem!