Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macOS version missing for Intel systems #296

Open
MacTerrassa opened this issue Dec 14, 2024 · 2 comments
Open

macOS version missing for Intel systems #296

MacTerrassa opened this issue Dec 14, 2024 · 2 comments

Comments

@MacTerrassa
Copy link

MacTerrassa commented Dec 14, 2024

Hello, a few days ago I saw that there was a new version of your interesting program Tockler, but I only saw a version for computers with the new Apple processor. As in many other programs, I see that they have chosen to generate an exclusive version for a type of system, but normally in this situation the rest of the programmers have chosen to maintain two versions adapted to each line of Apple processors (at least moment) or have opted for a universal version compatible with both architectures. In your case, I thought it prudent to wait to see if they published the Intel version later, but I see that it has been a long time now. Do you plan to provide this version or do you simply consider it obsolete and discontinue that Intel architecture in the case of macOS?

For what it's worth, in my opinion it is interesting that all the programs continue to support both processors, just as I find it interesting to support "obsolete" systems according to Apple's criteria. Obviously, at some point this stops being possible, either because of how difficult Apple makes it, or because they start using exclusive functions of the new systems/hardware. Although I could have sworn that this was not yet the case with Intel hardware, and that many systems with this processor are still in operation. Furthermore, one of the reasons for switching from using paid software to free software had always been precisely this: the broad support for "obsolete" systems without having to depend exclusively on the sales that can be generated or increased thanks to discontinuing support. for everything "obsolete". That is understandable in paid software/hardware, but not so much in free one. And it is an incredible argument to switch to this weight-free soft, even more so with the ecological awareness of recent years.

In your case, therefore, is it a lack of time to create it, a correctable oversight or simply that for you the time has come to abandon the support of these systems? Greetings, and thank you for your program that I can continue using, it looks very interesting and can be useful to many of us. Or at least, to those who can install it on their systems :-)

P.S. Message translated mechanically since I do not speak English. I apologize if I have not expressed myself correctly.

@MayGo
Copy link
Owner

MayGo commented Dec 14, 2024

Using https://github.com/electron-userland/electron-builder to build different versions.
If you find a setting to put https://github.com/MayGo/tockler/blob/master/electron/electron-builder.yml, I will gladly do it.

@MacTerrassa
Copy link
Author

Unfortunately, I don't know anything about programming. I wouldn't even know where to start to find the answer. Although I imagine it is some property that instead of mentioning arm64, it has to indicate "universal", or two alternatives: "arm64" and "x64". But I don't know if this has to be indicated in more than one place in the code, or if it has to be done both in the indicated file and in one more.
My question was more whether they were aware of this change, whether it was sought for some reason, or whether they simply hadn't checked that they only created the app for a macOS platform.
Thanks for your response. All the best.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants