8 ms·
Haven't those developers had access to the beta for months? What's the point in the beta if people aren't getting ready before the release?
by chrisseaton 7y ago
Haven't those developers had access to the beta for months? What's the point in the beta if people aren't getting ready before the release?
- ganoushoreilly 7y agoWith audio hardware it’s looking like substantial rewrites to core code because of underlying is changes. I think it’s just a lot of work on a short timeline for small development shops.
- jen729w 7y ago“Short timeline” assumes you didn’t see 64-bit coming a couple of years ago. Not saying it isn’t work, just that “I didn’t see it coming” isn’t much of an excuse.
- holy_city 7y agoI mean most software that's currently maintained has been 64-bit ready for a decade. The issue is that there's a lot of 3rd party ghostware that isn't, and 32 bit bridging to support that code has been popular for awhile. That software is a lot like vintage gear, there may be alternatives but they aren't the same, and that's the problem.
- sneakernets 7y agoThis is the same boat I'm in. Some of these programs were created only by one person, who can be impossible to track down and get a timely response.
- chrisseaton 7y agoSounds like the software was effectively already dead and it was best to move off it as soon as it became clear there was only one developer and they were hard to get hold of. The problem isn't with macOS.
- _ph_ 7y agoGoing to 64 bit can be a lot of work. So there is quite some software which is still lightly maintained for which there isn't a 64 bit update available. Software which has worked perfectly fine up to date.
- davrosthedalek 7y agoAdditionally, it has zero benefit for many applications from a performance stand point, or makes them even slower.
- chrisseaton 7y ago> it has zero benefit for many applications They literally can't run without porting, disregarding performance. The benefit is infinite!
- davrosthedalek 7y agoBut that's artificial, and you know it. The only reason for forcing 64bit is to lower Apple's support cost and push its bottom line.
- deleted 7y ago[deleted]
- chrisseaton 7y agoFine by me - sweeping out the dust.
- bikeshed 7y agoIf a program works fine, with no issues, why should companies be forced to update it simply because Apple decrees they no longer support 32 bit applications? "Sweeping the dust" is an absurd declaration.
- 7y ago
- 13415 7y agoIt's not just 64-bit though. There are also some fake-security "notarization" requirements that were notoriously vague and poorly documented for months, as well as some equally vague and unspecific threats that certain non-notarized applications might or might not cease to work on January 2020. I've been developing for Macs since the late 90s and have never seen less clear developer info. See the discussion here - and notice how confusing and contradicting the opinions about it are: https://news.ycombinator.com/item?id=21179970 https://news.ycombinator.com/item?id=21179970
- pier25 7y ago> “Short timeline” assumes you didn’t see 64-bit coming a couple of years ago. Or that you haven't had the resources to spend on it
- chrisseaton 7y agoIf you think the price of updating for 64-bit is expensive, you should see the price of not updating and not being able to run your software at all.
- pier25 7y agoThankfully I'm not in that position, but many companies can barely keep up with their day to day stuff. There is never time for doing something for the distant (or not so distant) future.
- w1nst0nsm1th 7y ago32 bit softwares run on 64 bit hardware. Period. It doesn't require maintenace on any platform, neither BSD, Linux or Windows. Depreciating 32 bit software is just an Apple trick to force financial turnover. It's the same reason why the deactivated sidecar for macbook older than 2016.
- jamienicol 7y agoIt's a very odd trick given that Catalina still supports my 7 year old macbook pro. Why not force me to upgrade sooner if it's all about the money? Not saying I agree with apple's decision, but it's surely it's just about reducing their own engineering costs.
- RantyDave 7y agoI think sidecar uses h265 so it's probably a question of the GPU either having dedicated h265 hardware or having enough grunt to run some kind of shader.
- klodolph 7y agoThe writing has been on the wall for 32-bit for literally over a decade and it’s not going to magically happen now just because support has been dropped. Imagine digging up an old project, recompiling it for 64-bit, and finding out that: 1. It doesn’t compile any more, with modern tools. 2. When you get it to compile, it crashes mysteriously. 3. When you get it to run, it again crashes mysteriously when you try a 64-bit build. Yes, there are a lot of “best practices” out there to avoid this. Any discussion of best practices is moot because people in the field have to work with actual practices and legacy code that might be full of undefined behavior, custom build systems, weird hacks, and lost tribal knowledge. And you are simply not given enough time to go through and fix it. This is not all about the 32-to-64 bit transition, but that’s the biggest part. Then consider the smaller shops—which might only have a couple of Apple devices altogether, and not a lot of spare developer-weeks to go through and test old plugins on new systems.
- deleted 7y ago[deleted]
- dmix 7y agoDo you have any specific examples of what would break because of this?
- positr0n 7y agoAny kind of pointer math that assumes a pointer is 4 bytes is an easy example.
- chrisseaton 7y agoWhy would you write code like that, except in a well-contained module?
- zamalek 7y agoIt doesn't matter why they decided to. They did. We all know better, we can all point fingers until we are blue in the face, but that doesn't change that people will lose access to software that they purchased. > except in a well-contained module? This is probably one of the best reasons. Game developers aren't entirely to blame here, middleware developers seem to be sticking to 32bit like balsamic glazing. Even if you could pry their cold dead hands off their archaic architecture, they'd probably make you pay full price for the 64bit upgrade. As for DAWs? Think about all the the VST plugins out there. Most of which probably aren't maintained and only exist as zip files on the artist's dropbox. Dropping 32bit is aspirationally sound. It's grossly inconsiderate of the very most obvious aspects of reality.
- Rebelgecko 7y agoFor a game where 95% of the revenue is made in the first year after release, the cost:benefit ratio probably doesn't work out. Especially for games where the rights situation isn't clear or the publisher is defunct
- gdubs 7y agoAudio is interesting in that it’s both a fundamental part of people’s day to day interactions with computers and devices, but also niche. A lot of audio developers are dealing with legacy code that has been growing over the years with a focus on pleasing a very specific user base. Just look at how long studios held onto OS9 because of the long tail of plugins they had that were awesome, but abandoned.
- AlanYx 7y agoFor many audio hardware drivers, it's not simply a matter of recompiling to 64-bit. Apple has deprecated a lot of things and seems to be trying to move everything over to AudioServerPlugins, which essentially requires a full rewrite of the drivers. The architecture isn't similar at all (AudioServerPlugins actually follow a Microsoft-style COM interface, among other things). I don't even think Apple makes any sample code for updating old Firewire drivers to run on Catalina, so it's a tough slog, and low-level CoreAudio expertise to update old drivers is getting scarce. Traffic on the CoreAudio developer mailing list is down to less than a dozen posts most months. There hasn't been a single post to the mailing list yet in October. I strongly suspect that some interface vendors are not going to update their 32 bit drivers for Catalina. (MOTU in particular is one, which kind of marks the end of an era because they used to be champions of some of the best CoreAudio features, like Firewire clock syncing.)
- chrisseaton 7y ago> I don't even think Apple makes any sample code for updating old Firewire drivers to run on Catalina Surely, surely it was obvious for years that Firewire is on the way out? Why are people so reactive and sluggish? People should be ready for change.
- Hammershaft 7y agoAs a independent dev I would rather spend my time working on new features and projects on an OS where my older projects continue to work fine rather than spend my time constantly playing catch up with Apples policies. This combined with the notarization requirement has pushed me to stop developing for Mac OS.
- dkonofalski 7y agoThis isn't just an OS thing, though, so I think that's crap. This change is a hardware change that's been forecast for literally years. To dismiss it as "playing catch up with Apple's policies" is nonsense.
- fbelzile 7y agoI recently updated my app to be macOS 10.15 compatible. Most of the changes were just annoying and difficult to debug, but some were glaring bugs related to Safari App Extensions which were show-stoppers. I really hope they fixed them before the release... 1) Although everything is "notorized," the Safari extensions aren't installed on app start up like it's supposed to in most cases. 2) The following API call works, UNTIL macOS wakes from sleep mode, in which case it always returns 'false.' SFSafariExtensionManager.getStateOfSafariExtension(...)
- saagarjha 7y ago> Although everything is "notorized," the Safari extensions aren't installed on app start up like it's supposed to in most cases Unfortunately, the only way I’ve found to figure out why this happens is to sprinkle breakpoints throughout Safari…
- pfranz 7y agoAudio stuff is notoriously prone to issues with updates. This has come up continuously since Classic Mac OS in the 90s. Audio guys are even sensitive to changing their physical setup. Outside of audio, I know of companies that ignore prerelease stuff because Apple has been known to change APIs during the beta period. It's not like Apple has a GM weeks before it is released publicly.
- dkonofalski 7y agoThey have both a developer beta and a public testing beta prior to release. To ignore pre-release access to a codebase that will inevitably become the public release is, in my opinion, stupid and a death sentence. You know it's coming. Sticking your fingers in your ears on the off-chance that something changes before release is really, really silly.
- pfranz 7y ago"Ignore" is likely an exaggeration. It sounds like many of these audio companies have tested the betas. People have reported many, many emails over the past week pleading for them not to upgrade yet. I would think that anyone with experience in pro audio would be very careful about any upgrades. The concern seems to be more of wasted time developing on a moving target. Often people report battery issues after major releases, people are reporting weird hangs after waking from sleep. Audio stuff is real-time in an OS that cannot guarantee it. Accommodating these things is a large undertaking and I'm sure there's gambling going on about what Apple will fix and what you can rewrite before Apple decides to ship.
- dkonofalski 7y agoBut no one is saying that these companies are forcing people to move to the new OS. The issue is that there's not even an option to move to the new OS for some users because their software literally can't run. It's not about chasing a moving target when the 64-bit change was announced 4+ years ago. Waiting until the very last possible moment and then complaining that 1 or 2 APIs changed leaves no one to blame but the developer that ignored the warnings and waited to fix their issues.
- ptah 7y agoa lot of developers won't update older versions of their software to be compatible either so a serious computer musician has learnt by now to stick with a system that is working