You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to get MarkEdit from the Mac App store on my mid-2012 MacBook Pro but:
WE could not complete your purchase.
MarkEdit can't be installed on "Macintosh HD"
because macOS version 12 or later is required.
Alas and alack macOS 12 or later cannot be installed because it's no longer supported by Apple. So the question is, is there a reason MarkEdit cannot be re-compiled to run on the older macOS?
Thanks for opening the ticket, I am afraid older OSes cannot be supported due to limited resources.
Is there a reason MarkEdit cannot be re-compiled to run on the older macOS?
This is a great question; I don't want to change my mind, but I would like to explain the theory.
For CoreEditor, the core editor, I believe it should work on macOS 11 or even older (mostly) flawlessly, but I didn't try.
For MarkEditMac, the Mac app, it works on at least macOS 12 because some UI techniques, such as SwiftUI bugs on older OSes. The Shortcuts feature even requires macOS 13.
Most importantly, I kept the mind of supporting latest two major versions during the entire development process, and I only have bandwidth to ensure that. Honestly speaking, majority of the tests are done on the latest version, even macOS 12 is not fully covered. By focusing on two major versions, it also allows me to use latest technologies and have less technical debt, that's the way to keep an app modern.
As a non-profit project, that's pretty much all I can do. I won't be surprised that someone can fork this project and make it work on macOS 11 or older, but I personally am not interested in it.
I, too, have a mid-2012 MBP that won't run anything newer than Catalina (10.15). If I were to try compiling this on Xcode 12.4, would you be available to help at all with that?
I, too, have a mid-2012 MBP that won't run anything newer than Catalina (10.15). If I were to try compiling this on Xcode 12.4, would you be available to help at all with that?
If that's directed at me then I'd have to decline because of reasons given by the developer. That is, bugs in the SwiftUI fixed in macOS 12. Besides I don't know Swift.
The developer has already indicated he's not inclined to support older macOS and frankly that's a righteous decision.
IMHO the way forward is to use the Opencore Legacy Patcher, something I have yet to look at seriously.
Activity
cyanzhong commentedon Apr 18, 2023
Thanks for opening the ticket, I am afraid older OSes cannot be supported due to limited resources.
This is a great question; I don't want to change my mind, but I would like to explain the theory.
For CoreEditor, the core editor, I believe it should work on macOS 11 or even older (mostly) flawlessly, but I didn't try.
For MarkEditMac, the Mac app, it works on at least macOS 12 because some UI techniques, such as SwiftUI bugs on older OSes. The Shortcuts feature even requires macOS 13.
Most importantly, I kept the mind of supporting latest two major versions during the entire development process, and I only have bandwidth to ensure that. Honestly speaking, majority of the tests are done on the latest version, even macOS 12 is not fully covered. By focusing on two major versions, it also allows me to use latest technologies and have less technical debt, that's the way to keep an app modern.
As a non-profit project, that's pretty much all I can do. I won't be surprised that someone can fork this project and make it work on macOS 11 or older, but I personally am not interested in it.
Thanks again and closing now.
johnblommers commentedon Apr 18, 2023
No problem. Your support strategy is very reasonable. Thanks again.
It may be time for me to try out the Opencore Legacy Patcher on my old MacBook Air.
AugustM commentedon Jul 29, 2023
I, too, have a mid-2012 MBP that won't run anything newer than Catalina (10.15). If I were to try compiling this on Xcode 12.4, would you be available to help at all with that?
johnblommers commentedon Jul 30, 2023
If that's directed at me then I'd have to decline because of reasons given by the developer. That is, bugs in the SwiftUI fixed in macOS 12. Besides I don't know Swift.
The developer has already indicated he's not inclined to support older macOS and frankly that's a righteous decision.
IMHO the way forward is to use the Opencore Legacy Patcher, something I have yet to look at seriously.