Came for the new programming language promised in the title, stayed for the comedy gold.
I'm staying on Mojave for now, both as a musician and as a programmer. Since I had to return my programming laptop I had borrowed that was running Mavericks, I only today ported over my code installed Xcode 9 and the latest Eclipse with Java JDK8 (to go along with me JDK6 that I keep hidden from Oracle so they don't delete it) and got everything up and running as it was previously. Xcode 9 seems to be the last version that plays nicely with legacy and I can still compile for Snow Leopard on up. This laptop is now frozen at Mojave as I have some legacy 32-bit stuff I wish to hang onto, both in VST and programming.
I'm just going to warn end-users that if they go Catalina, my software might work. Or it might not. They'll just have to manually okay it to run as I'm not a member of the Borg--er, Apple collective and I'm not about to shell out $100/year for some masochistic "privilege" to have my software poked, prodded and autographed by some bot. Since I'm not creating and installing kext files, which really should
be signed, there shouldn't be any issue.
I can understand the anger out there with the way Apple suddenly drops things, but it's not like we didn't know 32-bit was going away, or OpenGL is going away, or PPCs were going away, or Carbon was going away... Well, you get the idea. They do tend to give plenty of time for developers to rework their code. I'm sure the majority of you are ASL (Apple as a second language). I'm WSL and you should hear me swearing when I'm trying to solve a simple problem with their infuriatingly random 16-bit API (yes, it really is that old). Sailors get the vapors and faint dead away!
I do wish Apple would just sandbox their old technology so older software still worked, but ¯\_(ツ)_/¯ what can you do? It's their sandbox, I'm just playing in it.
I will jump on the auval bandwagon, though, and say they really, really, really need to fix the damned thing as it affects a huge chunk of their business, both audio and video. I get bit by this all the time, even having filed a bug report only to discover the second
time I dumped my cache, rebooted and ran auval and rebooted again, it finally worked. Color me embarrassed when I had to write back and apologize for the spurious report. I did blame it all on Apple though.