Open johnnyutahh opened 2 years ago
Unfortunately it is! However, I wouldn't stress updating just yet, for now the only practical difference is a bug fix regarding quotations in email titles (d561d9f5f6ae6a03264423a5642bf300c719a676) and I imagine 1.8.0 will work perfectly fine apart from those small bug fixes for a long time. I don't have any major changes planned for now.
I totally understand your reasoning and I've long hesitated to do a Swift rewrite because of backwards compatibility reasons. If something critical comes up, I might backport those updates to the 1.8.0 branch if a lot of people keep using Fastmate on Mojave.
(FWIW the bug fix above can be applied to 1.8.0 via a userscript should you need it)
Pointing out that while staying on Mojave is certainly preferable, considering the disaster that was Catalina and is Big Sur/Monterey, the reality is that Mojave is no longer receiving security patches.
So you need to figure out what you are going to do about that.
Keeping a backported version seems like quite a hassle, specifically now that Ventura is on the horizon and we've already had Catalina and Monterey following up after Mojave.
There's no technology reason to move to Big Sur/Monterey/Ventura. If you buy new hardware, you're forced to, otherwise why bother? If you want to look at pure stability, yea, stay on Mojave.
But the security patch issue would recommend at least moving to Catalina, even with all its issues. Problem is, Catalina will stop receiving security updates some time in Q4/2022.
In case it matters: I have upgraded to macOS Catalina and Fastmate functionally works on it (although on my current laptop its grown remarkably slow... not sure where the slowness issue might originate, could be Fastmail.com, some software config on Catalina, etc).
I'll probably upgrade to BigSur in Q4/2022 or sooner.
Thanks to everyone for all the help and support here!
Does Fastmate v1.8.0 still work on Mojave (10.14.6) for others? This combination started showing me a blank Fastmate screen on launch today, but previously worked reliably.
What I've tried so far:
Running Fastmate from terminal, it seems to get stuck after:
/Applications/Fastmate.app/Contents/MacOS $ ./Fastmate
2023-11-30 09:47:26.517 Fastmate[562:5662] Notification authorization granted: yes
Thanks for any input, just wondering if this is a totally local issue, or if others may be seeing this too starting around now. I don't know of anything that I've changed on this machine. Thanks.
Clarification: I'm not opening another issue, since the purpose of asking is just to check whether Fastmate v1.8.0 still works on last Mojave (10.14.6) for others.
Following up here, my blank-screen-on-launch problem was resolved. In case anyone else should run into this:
Phew.
@u35253 thanks for trying and updating with your findings!
Is v1.8.0 the last Mojave (10.14.6) supported build?
I can perfectly understand the reason(s) to move on. (I too manage software-development projects.)
fwiw, I'm often "One of the Last Person(s) to Upgrade," because I do not trust Apple to be an "Organization That Knows How to Properly Architecturally-Design and Test Software for Large Scale Reliability." (They've demonstrated this to me, repeatedly, especially with macOS.)
If the above is true, Fastmate.app will now probably be the first app that will motivate me to upgrade to Catalina. I'm sure there will be more to come. I'm not complaining, just noting. I work with reality as much as possible. 🤓