Mac OS Catalina: more trouble than it’s worth
morrick.me
morrick.me
Even after release it's still randomly losing files. Just yesterday my purchased music downloads just disappeared. No explanation (unless I trashed and emptied them in a fugue state). They were still showing as downloaded in the Music app, but when I tried to play them I got the "File missing. Locate?" dialog, so the Music app wasn't aware of this either. They weren't stored on iCloud Drive either, just the default local music folder, so it wasn't related to the iCloud Drive bug. This was a clean installation on a fresh disk, no third party system level junk, and after the unnumbered OS update they released a while ago.
There are quite a few other bugs too. macOS is still the better alternative to Windows, but the wow factor of "It just works!" is becoming rare and bug fatigue is creeping in.
Whoa, no. That is a huge code red for me as a creative. Especially in the music folder. I work at all crazy times of day and night, inspiration hits, and is often impossible to replace. Not alright.
Seems like it's chaos everywhere. Maybe a conspiracy by Big Backup.
[0] https://www.google.com/search?q=windows+update+deleted+docum...
Or I did indeed delete them myself but can’t recall. I had no reason to.
(so what you are saying is that the backup is not buggy? ;) or having cool AI perhaps deciding when a situation is not for backup because it is a wrong situation, now that would be a cute feature, working hard developing cool ML techniques to recognise and handle elementary system f* ups!)
So has my 2013 MBPr at home.
I still use mine almost every single day. It's a beast, and has been very reliable. Keyboard is WAY nicer to type on than the current generation. It's a little thicker and heavier, and lacks USB-c ports, but it's still damn fine.
Super reliable machine, still relevant performance-wise.
I plan on using it until it disintegrates.
Edit: I wonder if apple regret making these machines. They seem like a failure of planned obsolescence - at least, until new releases of OS X stop supporting them, which will probably be the next release, looking at the current horizon. Anyway. Totally broke the upgrade cycle for me - I have grown rather fond of my (t)rusty steed. My mother upgrades more often than I do, usually because she’s left every process open and running, and the machine is slow, and therefore she thinks she needs a new one.
It's a good point about the planned obsolescence: I've dropped this machine so many times it doesn't quite close properly, the aluminium around the top of both USB ports and the HDMI port are deformed, I've had to clean metal particles out of the MagSafe2 connector many times, I work in a metal fabrication workshop so metal particles follow me everywhere.
Six year old machine still in reasonably good condition and works fine.
But second-order (and beyond), particularly from the perspective of the companies, I'm less sure what's best, or if there even is a global, objective 'best'.
Consider the most radically distant point you can imagine in 'self-supporting human group' configuration space, that's still capable of making something like a MacBook. What does it look like? How is funded/financed/supported? Is it temporary, i.e. more like a one-time project like making a movie or a video game? Or is it, somehow, a 'going concern'?
The 'going concern' attribute is one that I think is perhaps under-appreciated. One thing that companies, and other long-lived organizations, do well is in organizing people with specific expertise long-term. Think about making a computer, or a washer, or any physical product. Surely the people that make those things, that have done so for an extended period, have a huge amount of detailed knowledge, and wisdom, pertaining to making the specific things they make. What would be lost by them NOT having made the same things for so long? What would our computers, or washers, or pencils, be like if they were all produced by something more like a Kickstarter project?
Imagine another possible world where the 2013 MacBooks were just as good as in our world, but also intended to last indefinitely, perhaps more easily repairable, or made of more common or standard components somehow. Say they lasted 30 years, easily, before needing to be replaced. How is Apple different in this other world? How do they retain engineers like they do now? How do Apple's competitors do this? And, maybe most importantly, how much do MacBooks cost in this other world?
If your old products are still running fine that's only good publicity and generates word-of-mouth credibility.
Windows 10 vanilla is probably pretty nice.
[edited to clarify the source of the problem]
I wouldn't use exactly those words, more like 'not really capable', but yeah, definitely possible. Due to circumstances I can run my own machines out of IT's hands. This is a pretty large university, yet: my Linux, Windows 7 and 10 machines are what I'd call rock solid even despite aged hardware. Better spec'd machines running the same OS managed by IT seem to be riddled with random bugs and in case of Windows also slower.
Not up to quite the usual quality, definitely.
Which operating system? This isn't about comparing hardware.
I'm on the latest MBPr and I love it; the problems are coming from Catalina.
I usually only update when I either need to because a program I want to run doesn't support the old OS, or the OS stops receiving security updates, or if I get really bored one night.
> it is still the better alternative to Windows
I’m not sure what kind of Stockholm-syndrome it takes to put these two sentences in the same post.
This is just crazy.
BAD ---X-----Y----Z----- GOOD
Given the standard definitions of "better" and "worse", Y needs to regress substantially to put it behind X.Randomly losing files is not at all acceptable and IMO puts it below that minimum. The prettiest font-rendering in the world won’t matter if your documents are gone.
Catalina's file loss was confined to iCloud Drive during the beta, and what happened to me was in the Music app after release.
I grew up with Windows, and the recent problems with macOS are still not bad enough to make me want to go back to Microsoft.
macOS is the occasional burn, while Windows is a constant assault on multiple fronts. UI, spyware, performance, security, consistency, aesthetics, accessibility, lack of a multi-platform ecosystem (phone/tablet/TV) and bugs of its own like every other software.
[0] https://www.google.com/search?q=windows+update+deleted+docum...
And Windows updates have had that problem as well, so the whole scale just shifts.
Having read most of the comments, I got the impression that you could correlate them with age. Younger people are all "Catalina works for me! Progress! Change is necessary! What are you whining about?!". Perhaps I can relate because I've been using computers for >25 years now, and I'd like to see a division between rapidly changing things (like my applications) and foundation-type stuff that I need to get work done (like computers and operating systems).
> Apple has more or less always said "Jump!" and users and developers have always been expected to reply, "How high?" That attitude, We know what’s best for you, was tolerable — at times even welcome — when it was crystal clear that Apple really knew what was best.
Aside from the bugs, which I'm sure will get resolved in updates, Catalina takes a lot more than it gives.
My current solution is just to keep a bootable Mojave volume around, but long term I don't know.
I thought about doing this as a commercial project, but it's likely I'm the only one who cares (I have a large archive of historical photos organized using Aperture).
One thing I've learned: from now on, I will organize my image archives using my own software. I am done with trusting any large company.
I don’t think that’s it.
Once upon a time a Rolex was a serious tool for professional pilots and divers but now it’s a status symbol. It still basically tells the time but no one buys it for that.
Once upon a time a Mac...
By "courageously" taking things away from users, they frustrate older users who know how to do what they want for themselves, but Apple seems to be counting on a new generation of users who never learned to do things for themselves to be just fine with letting Apple do them. I always appreciated Apple's dedication to "quality", but the quality involved in computers as "bicycles for the mind" is not the Apple of today, where "quality" is about looking young, hip, fashionable, and somewhat wealthy.
Short answer: I'm definitely not young—I started on an Apple II in high school.
I do keep my software current and pay attention to things. I lived through 68000 -> PowerPC -> Intel, so I know how this goes.
I've been running Catalina since the late betas and haven't experienced the issues others have, other than my old Apple Keyboard with Numeric Keypad not working with Catalina, which is kinda annoying, since I really like the extra keys, etc. instead of the Bluetooth keyboard that came with the iMac.
Know what I did?
I submitted a bug report to Apple.
There's no doubt that Catalina (and iOS 13 for that matter) are more buggy than recent past upgrades, which is not good.
I don't think it's Apple not caring; I think they're trying to do a whole lot with overlapping groups. If the rumors are true and there's a 16-inch MacBook Pro about to come out and ARM Macs will likely become a thing in 2020, I suspect a lot of engineers are juggling multiple projects across multiple groups and this is the result.
I also switched to Zsh before I upgraded so I'd have my config all set before hand. So far, so good. And thank goodness for Homebrew and how quickly it had Catalina-compatible packages ready to go.
Wait, how hard is it going to be to keep running Bash?
I've wasted hours this week wrestling with issues in Xcode 11 and the command line tools because of bugs in Apple's code.
The bluetooth on my MBP2015 constantly drops, requiring a full restart in order to work again. Apps run slow whenever I have multiple monitors attached.
And don't get me started on the MBP2018 hardware, that damn keyboard keeps sticking.
I am not impressed with Apple's recent offerings.
What I have noticed is that Apple hardware is highly inconsistent these days. I think it's a function of the Retina displays. The non retina Macbook air with such an underpowered processor sesms to work better than the current Macbook air.
OTOH the Macbook pro is seemingly working great. The 1.4GHz entry model outclasses the older generations by leaps and bounds. I have also started appreciating the touch bar, despite being a heavy vim user. The one touch shortcuts for da y to day stuff like zoom sharing desktops etc are very welcome.
I guess my point is something doesn't have to be "good OR bad" for some people to like it and others to dislike it. Pretty sure it can be both at the same time, depending on where you're looking from.
How does the Capture One Pro version work for you?
Either way, this is an extremely long blog post to say basically just "I don't like change, and I'm not willing to see change as a potential improvement to try to accept it".
I don't like change when it unnecessarily breaks things that used to work just fine. I don't like change when it is haphazardly imposed on a yearly basis by a company which has clearly stopped caring about Mac OS as far as management is involved.
I used to like change more when it actually made me work better, when the advantages clearly outweighed the downsides, when progress and improvements were noticeable and thoughtfully implemented.
But hey, that's me.
>Hello! I am the author, and no, I haven't tried Catalina because, as I state at the very end of my article: >"Both my main Macs are really working flawlessly at the moment, and Catalina is beta-quality software that’s likely to give me headaches I don’t need right now. Who knows, maybe down the road I could acquire a cheap used Mac that can run Catalina (something like a 2014 Mac mini) and use it as a test machine. As things are now, I absolutely do not want Catalina to mess with my current setups and data."
In all seriousness, older people are more opposed to UI and other types of change.
> I don't like change when it unnecessarily breaks things that used to work just fine.
> I used to like change more when it actually made me work better, when the advantages clearly outweighed the downsides, when progress and improvements were noticeable and thoughtfully implemented.
He is opposed to changes that 1) break things that used to work fine, 2) do not make him work better, and so on, you get the idea. If those changes make him work better, or when the advantages clearly outweigh the downsides, and when improvements are noticeable and thoughtfully implemented, then he is all in favor of those changes, i.e. not opposed to changes in general, just some changes that do not meet some criteria.
The arguments for building emulators into the OS are weak. A minority of users running old operating systems in VMs while the majority get a sleeker, better maintained and thus hopefully more secure OS. That is a fair tradeoff.
Pulling native 32-bit support may be 2019’s laptop-with-no-disk-drive drama.
This is by definition what change is. It's an improvement, and if changes didn't break things there'd never be progress and nothing would get changed.
I don't know about you, but I value working software and it'll probably be six months before I consider dropping Mojave.
Multiple data loss bugs? Arbitrarily killing all 32-bit apps? No thanks, I'll wait.
It's not that. We just have more experience of Change, and know that Change Without Purpose rarely provides any benefit.
It's certainly disingenuous to have a clickbait headline "Mac OS Catalina: more trouble than it's worth" when it's missing "as explained by someone who doesn't use music, photos, TV, reminders, notes, or really anything else from the Apple software ecosystem".
The problem is when that context is stripped away by aggregation sites like this one where tons of articles we read are from publishers and the expectation might be that the author did some research, tried different things, and was trying to write from a more objective or all encompassing view point.
I have the same problem with articles where the title will read like it's going to be a regular news article but instead it's a 6000 word story on the authors journey to uncover the information and how it made them feel yadda yadda. Not really the publishers fault, I'm sure their reader base knows what to expect (I know I've learned to stop clicking links to The Atlantic), but ends up misleading the potential reader from elsewhere a bit.
When this happens I think the fault is with the aggregator not allowing or enforcing proper information labelling. Not the author being disingenuous.
I'm only saying this because I updated to Catalina without going through the betas first and I haven't had any issues whatsoever. To read something like this that is so negative about it seems like astroturfing or manipulation, especially when the only articles this website has ever posted on HN are all critical of Apple.
macOS is a product on its own, especially if you come from the hardware pespective, wanting for instance a iMac Pro and seeing the OS that comes with it as a glorified hardware manager.
Is macOS Catalina the best OS for your machine ? Is it genuinely better than the precedent version ?
That's a question worth pondering.
Apple wants macOS to be a safe walled garden like iOS and Chromebooks. I am fine with this, but I also have a very nice Linux laptop to play with.
I expect organized crime and most governments to continue hacking activities so it makes sense having my Apple devices locked down as much as possible. I avoid arbitrary web browsing on my Linux laptop and just use it for coding.
"Both my main Macs are really working flawlessly at the moment, and Catalina is beta-quality software that’s likely to give me headaches I don’t need right now. Who knows, maybe down the road I could acquire a cheap used Mac that can run Catalina (something like a 2014 Mac mini) and use it as a test machine. As things are now, I absolutely do not want Catalina to mess with my current setups and data."
I'll add — I'm in a position (work-wise) where I can't afford to risk Catalina messing with my current setups and data.
Personally for me this has been the smoothest upgrade ever! Literally no apps are broken and no data lost.
Edit: typos and clarified that I read the blog.
What makes web browsers less secure on Linux than on macOS?
But we have a number of solutions for running things in containers if you just use them. Early on firejail was popular, these days I just run nspawn containers for browser instances and bind mount in some stuff for a shared Downloads directory etc.
I can't speak to how that compares to OSX as I've never used it, but it is worth noting that the security story on Linux can range from bad to somewhat OK depending on your setup.
Edit:
In responses people seem to be completely ignoring that I already stated above in my original comment that I can't speak to how it compares to OSX. I don't know what OSX is doing for application sandboxing defaults.
I can however speak with some authority on the Linux situation. And today, if you're running firefox/chrome as your regular user as installed by apt/yum etc, without any additional sandboxing, and that user has access to secrets like ssh/gpg private keys, you're being unnecessarily reckless. And unfortunately that is basically the default way browsers are run today on most distributions
This is a major reason why the Flatpak/GNOME people have been working so hard on portals and namespaces are an integral component of the runtime. It's not just about application distribution. They're trying to close a major security hole in desktop linux as it's often used today. They want applications like the browser run in its own namespaces with just the minimum of host filesystem paths bind mounted in.
There's absolutely no reason for your browser process to have the ability to access all of your private keys, just because they happen to be under the home directory it happens to have access to, full stop.
What are you talking about? You're saying that a random website is given unrestricted file access to everything the user can access. Can you back that up with a concrete example or a link explaining the issue or something?
We've had plenty of browser exploits for any given browser, sandboxing the entire program a la containers is the most effective mitigation outside of running it in a dedicated vm.
What does the possible existence of exploits have to do with macOS being more secure than Linux? macOS can also have exploits.
I don't understand where your claim that there's a specific risk of unrestrained file access to websites comes from. In my eyes, saying that it could be true because exploits could exist nullifies everything you said.
You could apply that argument to everything: There is a substantial risk in iPhones giving websites unrestrained access to making phone calls on your behalf because all it takes is an exploit.
Relying on the browser alone for sandboxing is problematic as the dominant browsers can't really be trusted. It's best to sandbox the entire program, in addition to their internal sandboxing techniques.
One person is losing file site awful. One person finds out works isn't suprising, it just shows apple managed to release an OS which isn't buggy for every user.
Most likely the bug they encountered happens in a specific scenario, but regardless, "personal anecdote" or "it works for me" are not appropriate ways to respond to a bug report, let alone one about data loss.
I only have one Apple device (an iPhone), and even in that simple use case I have sync issues from time to time. It's mainly previously deleted things that appear back on the device (photos, reminders…).
Apple isn't good at this.
Thanks for being my beta tester!
My in laws are very happy on Ubuntu Mate, it looks like old Windows (after changing one setting), and the Pictures and the email app are simple and clean. It's all they do.
Every time I’ve used macOS (I’ve had three MacBooks and two iMacs) I have to fight them. And I’m not up for that.
That's how I organize photos on Mac OS. You don't have to use the Photos app. Periodically I dump all the photos from my phone and other devices and sort them in folders by year (and sometimes sub-folders for vacations and other big events). I only use Photos to get at the pictures from my phone if I need to look at them before the dump.
Generally slower to browse and open previews.
I have this too, I planned to look into it this weekend to see if there is a fix. I have moved my photos library to my synology just before upgrade to Catalina, as well having a little one, your photos exponentially increase. When I want to sync now it says it syncing, 'finishes within 3 seconds' and didn't sync at all..
(The Metro one, not the photo viewer in explorer)
Edit: And someone else replied, the DPI/font stuff seems to be fixed as it was driving me crazy in Mojave. The upgrade is worth a try for that alone.
[1] https://www.pro-tools-expert.com/production-expert-1/2019/9/...
Apple orchestrated a much smoother transition from OS 9 to OS X and RISC to x84 than from 32bit to 64bit.
During that entire decade, Apple issued steadily-increasing warnings to users that eventually, the 32-bit support would cease.
Seems like a smooth transition to me.
You're not supposed to. The fault lies with the developers of these apps that knew the change was coming and didn't do anything about it.
> How am I supposed to replace unmaintained/old software when there's no new 64-bit, notarized version of it?
You are not, and therein lies the problem that apparently some people are incapable of recognizing. It was a terrible decision, and some guy tried to justify it with "technical debt", but somehow other OSes are perfectly capable of handling it while Apple cannot. Why is that?
In any case, I think it was a silly decision to "force" the customer to pick between old vs new software, but I am sure they can afford it. People will probably forgive them for it, and then completely forget about it. New users in the future probably will not even have anything to forget (or forgive), unless they want to run "really old" software, in which case people will just boo on them, and say "times change, technologies change, you gotta adapt, man" and the like which seems to be the case today with respective to both old software and hardware.
This is not true of my 32 bit apps.
For some reason people were still releasing 32 bit apps as late as this year. Maybe it was because Apple didn't warn users about this until Mojave was released, which was barely a year ago.
I wish I had my HDMI and SD card ports back though.
Btw, Apple's reportedly putting the Esc key back on the new MB Pros. And they still have an audio jack. And they still have USB.
Did they?
I only saw warnings in Mojave.
I'm and Apple registered dev. I remember in 2016-2017 when it was announced for iOS and that was just 2-3 years ago. For macOS I think the first time I heard about it was about a year ago.
I would expect such a big deprecation to be announced at least a couple of years in advance if not more, but Apple generally does a terrible job at letting you know what will happen 2+ years down the road.
There was a whole machine architecture change, and most people didn't even notice.
It’s extremely disappointing. Apple just ensured my next machine will run Windows.
Same here. Counter Strike Source. Shame, Valve!
I mostly use it for development, everything still works.
My only annoyance so far has been SideCar, it just never works the first time, I have to switch from second display to mirror, then back to second display to make it work.
https://support.apple.com/en-in/HT210380#systemrequirements
I use a 2015 MBP too, so I'm glad to hear it does work and thanks for the workaround.
Once it works, it's actually really great, I mainly use it for my terminal and browser debug tools. It's nice to have some extra space.
EDIT: my Q was more likely to woutr_be, where it was enabled..
Other than that, it’s been pretty good. Battery life improvement, seems faster, etc.
> it just never works the first time
Make up your mind. These two statements are not compatible.
The second one is specifically referring to SideCar as an individual feature.
This seems to be the heart of the post. I see the value in stable, unchanging things, but I also have to believe the designers at Apple are trying to make things better, and I think that is honorable.
Except they're not trying to make things better. They're just changing things - often ignoring their own UI guidelines to do so - and introducing bugs that cause data loss at the same time.
Updates shouldn't cause data loss - especially for something as critical as email.
I would really love to see every other major release of macOS and iOS to be a bug-fix release rather than a "lets change all the things" release.
Here fucking here!
Unwanted help isn't help at all
That's the smallest thing in it.
Supporting the upgrade process at an enterprise level is especially difficult. PPPC's must be created to get anything connected to the camera, mic, keyboard or screen. The walls to the rose garden of macOS are higher.
Could OS software be built like Ubuntu? With LTS in the model for 5 years? + Security patches when necessary?
Apple has, for the entirety of Mac OS X and macOS, has spent a substantial amount of time enhancing media and mobile quality of life. Catalina is no different. Take a stroll down memory lane: iTunes (was the amalgamation of the first three apps you mentioned), DVD playback, iChat, .Mac syncing, Dashboard (Widgets), Back to My Mac, MobileMe, Front Row, Photo Booth, App Store, iMovie, iPhoto, iChat, AirDrop, Messages, FaceTime, Game Center, and iCloud.
Some of the apps you mention have been getting updates for longer than just Catalina. Photos was launched in Yosemite, while Notes and Reminders launched in Mountain Lion.
I am sure we can both imagine people who were disappointed in 2007 when Apple redesigned Mail and were posting on digg about how Lion is more trouble than it's worth.
As for the lack of 32-bit support, this is really not a sticking point for customers who pay to have their applications supported. If a product is no longer being developed, why is it that you blame Apple's software update?
Oh, and another thing that isn't new: initially buggy releases of macOS
Was it to the same extent that people are complaining about MacOS Catalina though? This is the first update that I don't like, and it's because of the lack of 32-bit support. Being forewarned about 32-bit going away doesn't make my 32-bit applications run on Catalina.
True, but the combined bugginess of iOS 13 and Catalina is astonishing. Shit really went wrong with this cycle. I am sure they will get it under control, but it’s so bad right now that I’ve actually told people considering entering the Apple ecosystem to hold off for a while until this dumpster fire is put out.
So overall, I tend to think that there are too frequent upgrades and that I don't need them. But overall, I'm still a satisfied mac user so I give Apple the benefice of the doubt.
I will usually wait almost 6 months to do the upgrade because of that, and then usually over a weekend/holiday so I don't lose work time trying to deal with the troubles that can arise.
Its pretty much crap. I'll wait until 10.16 is out and then upgrade to the 10.15 that isn't crap.
- While I'm flattered by the attention my piece got by 'making Hacker News', it is simply a personal view and a personal disappointment towards the direction Apple is going with Mac OS. It's not a prescriptive article. I'm not telling people to avoid upgrading to Mac OS 10.15. It's your Mac, it's your work, it's your data, it's your time. Do whatever you please.
My decision to not upgrading is the result of a lot of time spent gathering information and evaluating costs and benefits of the upgrade. And my conclusion, as I clearly stated in the article, is that I'm not upgrading because "what Catalina takes away from me is more than what it gives me."
I also took the opportunity of sharing a few reflections and my criticism towards Apple's recent treatment of Mac OS. Whatever the underlying causes, it's undeniable that Mac OS is not as robust, consistent, and well-designed as it used to be. It wasn't bug-free before. Nothing is bug-free. But I remember past versions very well. I use a variety of Macs of older vintages, so I still use older Mac OS X versions. The degrade in software quality and system stability isn't a matter of opinion. It's out there to see.
And yes, I don't like the direction Apple has been moving after Steve Jobs's passing. That's an entirely personal preference, and I respect the point of view of those who, instead, love what Tim Cook & Co. are doing. I'm not really 'complaining' that Apple's not doing things 'my way'. However, as someone who has been using computers for 38 years and Macs for 30, as someone who knows a thing or two about user interfaces, user interaction and user experience, I think I'm allowed to share a few criticisms about the direction Mac OS is going without being called a 'whiny entitled teenager'.
I try to approach technology by focusing more on the forest than a single tree, and sometimes I struggle to see all this 'progress' and 'future' other tech geeks keep talking about.
Technology should adapt to us, not the other way round. Progress should mean making things better, improve what we do with the help of computers and devices. Instead, as I wrote, "I also notice that — for everything to keep working smoothly — you have to do more work than before. It just works, with Apple products, has lost the frequency and consistency it once had. It is a strange progress when you keep feeling the sting of two steps back for every step forward."
Just look up comment after any major upgrade of OS X. It will be a deja-vu. People compare the last x.x.xx release with tons of bugfixes to the y.0.00 and are so shocked there are bugs. Well, duh.
>> I think I'm allowed to share a few criticisms about the direction Mac OS is going without being called a 'whiny entitled teenager'.
I do as well - and, to boot - I wholeheartedly agree with your critique for the most part.
>> Progress should mean making things better, improve what we do with the help of computers and devices.
For sure, and removing access to a lot of my commonly-used applications doesn't help with that, for sure.
> 5400 rpm hard drive as its main internal volume
Regardless of OS, the author _really_ needs to bail on the 5400rpm HDD and get a solid state disk in there... especially if you're gonna call it a workhorse!
Biggest reason I will never buy another Mac. It seems like they just don't want this to be the case. Terrible for the environment.
Source: I have been looking for cheap ways to have fast external disks for years. 4 years ago I went with a hacked Buffalo LinkStation (it’s one of the few products that can be easily taken apart, so I swapped its slow disk with an SSD), and now I just ordered a new TB3 enclosure from aliexpress (plus a super-fast disk from a reputable source) to replace it. External TB disks are still overpriced, let alone TB3. I honestly don’t know why that is - I suspect it’s something to do with the main market being Apple users with deep pockets and limited knowledge.
Apple themselves needs to bail on the 5400rpm HDD
I switched to using macOS just recently (Mojave being the first I really used), so I might not know.
I notice myself being less and less open to radical new change and being more willing (and able) to just stick to something that works for me. I have tinkered a fair lot in my days, mainly on Linux.
Catalina has been fine for me, but I probably have a different use-case.
Just last night I spent all day trying to do some work on a friend's 2011 or 2012 MBP (16 GBs RAM, i7, should be fully capable). They needed Windows 10 for some special software, and wanted some help cleaning the hard drive to make room for the partition. After hours and hours of fighting tools and trying to work around Boot Camp Assistant limitations (it insisted on always reformatting as exFAT, in spite of Win10's 4+ GB .wim files), I finally determined that it was probably all fixed in a later version of macOS and proceeded to update her to Mojave.
Fast forward another hour and we're stuck in a bootloop of failing Mojave installs with some barebones diagnostics and repair tools that do nothing.
Thank GOD she had months worth of complete Time Machine backups we could easily restore.
But it's insane to me that a system update served by the App Store in the golden path on a piece of hardware still within it's support lifecycle could fail so catastrophically. I've given the middle finger to Windows' "Don't turn off this computer" messages scores of times, and it's always been able to boot up again just fine. As of late, I've not even experienced the need to do "Automatic Startup Repair" like the old days.
Is Apple really slipping that hard right now?
exFAT doesn't have a 4gb limitation like FAT32
Standards based software engineering seems to be all but dead in consumer apps (it never existed?). Clearly, there is no explicit guarantee of longevity to your data and the metadata (edits, collections, albums, tags, comments) you create upon your own data.
This is a really poor way to live one's digital life.
Do you think about longevity of your data+metadata? What's your setup deal with this?
Funnily enough, the cloud account is the one that worries me the most. The data I want to keep includes some indie movies and music that I fear might disappear from the internet (like mixtapes from very indie local groups I listened as a teenager that nobody cares about) and I fear the whole account might be suspended if at some point they set up a copyright filter or something.
In my case that means a chunk of SFTP-based storage, and rclone to make that storage encrypted at-rest.
The 64 bit transition was a compatibility break that enabled shedding technical debt, like NeXT-isms that no longer applied. In particular it added the ObjC 2 runtime, which allowed features like adding a variable to a class without needing to recompile subclasses.
So long as 32 bit is supported, it is difficult for Apple to use these features internally. If you add a variable to a class you break the 32 bit system. If you add a variable conditionally under an #ifdef then it is annoying to manage the separate build configurations, or disparate 32bit/64bit behaviors.
This only applies to the Mac; iOS always had the modern runtime. But macOS engineers are very very happy to see 32 bit go because it was painful to support.
Linux has some 32bit shims in the kernel and a few separate syscalls, but userland does the separate libraries approach where all 32bit libs are separate than 64bit libraries. So the kernel pays a small cost, while userland needs to maintain separate versions of the libraries - which often costs very little (many can simply be recompiled, this is open source after all), but can bite the maintainer sometimes.
MacOS uses the fat binaries approach, where every binary carries all the arch versions. I don't think the system supports a different method - so Mac pays a bigger cost than Windows or Linux in order to maintain 32 bit. Also Mac kernel API is unstable by design, and I guess Apple would like to drop some older stuff. For better or worse that's the Apple Way - they don't maintain anywhere as much backward compat as other platforms.
[1]: https://apps.apple.com/us/app/audiobook-binder/id413969927
I cloned the drive onto an external SSD with no other changes. Immediately she had a usable machine, and she now enjoys using it again.
That does mean OS/DE devs are hitting disk way the hell too often and just hoping modern disk speed makes it harder to notice, but there's no way that's not adding up to some real (but less crippling) latency even on SSD-equipped systems.
Has anyone else noticed Catalina doesn't remember external display rotation when waking from sleep?
There have been a few instances where it somehow restores the proper rotation, but most of the time I am forced to put it back manually. I don't want a "workaround" via AppleScript or a hotkey to easily set it back to what I had configured, I just want it to work like it always had!
Then I hit the "configuring macOS" forever bug after the second install attempt (just force reboot).
I think both of these installer bugs have been addressed in the recent supplemental update to 10.15.0 for any downloads going forward. Despite all these issues, things have been fine actually running Catalina, but I'd wait a few point releases if I did it again. The whole thing 'feels' very fragile, for lack of a better word — mostly due to the online conversation about it.
I'm definitely leaving my home theater Mac Mini on 10.14 for the foreseeable future after reading about the HDMI issues.
Ultimately, I find it best to just suck it up and upgrade and use virtualization to run specific stuff.
Mac is the easiest for me to have a daily driver browser while also being useful for most dev and basic Unix user tasks.
On iOS it seeem even worse, with yearly releases breaking many apps; Apple's aggressive ABI changes offload a large maintenance burden onto app developers, who have to keep updating their apps every year just to keep them working the same way.
Windows seems to do a lot better, and game consoles do even better: with the exception of multiplayer games whose servers get shut down after a year or two, most games keep working indefinitely across firmware revisions.
Ideally, apps that work on one iOS release will continue working on the next with no change in behavior, as Apple checks when apps were linked and will opt out of the new behavior.
If you mostly use a browser/terminal for everything its nothing to worry about.
I will say that Podcasts app kinda sucks, just like the iPhone one it's needlessly confusing when trying to open the show's page with the episode list, instead of just "recently played" or w/e you've downloaded. It tries too hard to be clever, while abandoning simple descended by when the show was added. idk why they can't do both.
The only difference I noticed (and I don't really have time to obsess over little details) - was that WINE was broken.
As far as my work-laptop goes, I'm just going to hold off. I don't really need any of the new features; and I don't rely on WINE for anything I do for work. I just don't have any strong feelings for a major OS X update right now.
I think the last time I even used Safari was about 5 years ago for testing a website I was developing.
Lost me at UIs shouldn't change in twenty years
I generally agree with the author, I don't have anything else in the Apple ecosystem so most of the new features are largely worthless to me compared to what I have to give up.
So, they're doing what you want?
It’s like Apple are trying to nudge me into being better at responding to emails. Is there a PM at Apple watching an engagement metric increase? With my personal email?!
Well that is of course all silly conjecture and I doubt its anything more than a bug, but if it were true then that’s some real Silicon Valley stuff right there.
Maybe Apple own stock in whichever paper manufacturer is post commonly used for printing emails from meemaw. More emails really pushes the needle on those paper sales! Q4 performance summary cycle bonuses all round!
1. Creeping storage corruption that is exposed by the upgrade. 2. Latent configuration issues from running the betas.
Personal experience: I have had several issues with apps on a machine that went through all the betas. Had to spend some quality time with Console to sort things out. Zero issues with machines that upgraded untouched by betas.
Hours of backing up later, it just upgraded off the beta train perfectly, though didn't explain why it took some valid files (perhaps cached from iCloud) and dumped them into a folder.
Nothing I use is breaking, none of my workflows or habits needed changing, it was fine.
The author ought to take a good, long look in the mirror and ask if maybe they've got some problems with change.
I dunno... to me it sounds like someone complaining that their new computer can't run DooM anymore because it didn't come with a 3.5" floppy drive. Yes, you can run DooM still but not in the very specific, needlessly encumbered method you want to run it in. Times change, technology changes, and it's just not productive to lock yourself in to something and then complain when what you've locked yourself into doesn't work out the way you predicted. Keep using the old OS. Just don't act surprised and attacked when it doesn't work anymore years from now.
A customer is legitimately entitled to upgrades that aren't actually downgrades.
> Apple isn't forcing anyone to upgrade at all.
> Just don't act surprised and attacked when it doesn't work anymore years from now.
Well... if Apple isn't forcing people to upgrade now, but will later, then there's still grounds for complaint.
An unhappy customer always has the right, nay, duty, to publicly complain until the business changes its behavior.
No, they are not. This isn't an upgrade to their existing OS like a patch release. This is a new OS completely and developers were all warned years in advance that Catalina would drop 32-bit support. This is not a downgrade in the slightest.
>but will later
I have a Mac Mini from 2005 that still runs MacOS Leopard just as well as the day I bought it. I can't install all the latest, greatest software on it and I can't even access every website anymore (TLS updates and all that) but it still functions as good, if not better, than it did when I first bought it and runs all the software that's still installed on it.
No MacOS update has ever been forced or mandatory. Ever.
The customer is not always right but I'm pretty sure offering an OS upgrade is doing right by the customer considering it doesn't cost anything and, for most people, adds far more than it takes away and is, again, optional.
The fact that macOS updates are optional, and you can downgrade at any time, really does help a great deal here. However, Apple's three years of security updates per release isn't much.
And that is totally fine for you to feel that way. You are not, however, entitled to some kind of reparation for that and, if you wrote a diatribe that was comparable to the OP, I would also say that you're making a mountain out of a molehill.
Something being disappointing to you, individually, does not make it a massive failure for everyone.
I don't disagree with your point as a whole, but Catalina is is not a new OS, it's an incremental upgrade.
And complaining? Complaining about what? You act as if Apple is bricking computers if you don't upgrade...
But back then, they also supported old releases for longer.
I actually suspect this was part of Apple's internal calculus, or part of it. "Free upgrades will get installed by more people, so we can drop old releases more quickly." A fine tradeoff under some circumstances, but right now, the old way of things is looking quite appealing.
I don't think that's true. I've been an Apple user since just before OS X's release and the support level was always 2 versions back since like Panther.
Is it? It's not really clear to me there's any sort of hard technical limit that requires operating systems to abandon components that support older software.
There may be an economic argument that every team has a limited amount of attention and resources, and older libraries/apis/layers may compete with newer ones, and that argument may even have some merit if the newer stuff is categorically better.
But, OTOH, there's MS's backward's compatibility, so it's clear that some platform owners can bear the cost just fine. Too bad Apple just doesn't make enough money for that, I suppose. :/
Perhaps they could think differently and charge users who want to stay on older versions of macOS for the updates. That'd provide a signal of how valuable it actually is and perhaps even a supporting revenue stream.
Unless resources aren't actually the issue.
That decision, though, comes with the consequence that you likely won't be able to run new software. If you're not worried about new software and don't want to be until the point comes where you need new software, the updates have always been optional.
There is also no particular reason that I can tell why certain features are only added to the latest OS, though we have become desensitized to this. For example - why can't the ability to extend the Mac desktop to the iPad be added to Mojave?
Likely because there's a part of the iCloud stack that was set up by code that's not in Mojave. Additionally, that was never advertised as a feature of Mojave so I fail to see why there would be any expectation that this would be added to Mojave.
That's my point - if it's a software requirement then it can in theory be added to say Mojave 10.14.7.
> that was never advertised as a feature of Mojave so I fail to see why there would be any expectation that this would be added to Mojave
This is software, so I highly doubt that the real reason is technical (why can't the code be added to Mojave?) just that Apple feels they may suffer long term if they reward people for not updating to major releases, or it's too costly to maintain so many forks of macOS.
I wouldn't care nearly as much if Catalina didn't drop support for 32-bit apps.
There's wasn't much wrong with being able to run it but there's a hell of a lot of technical debt that comes with being able to support and maintain it. Every binary that needed to run on 32 and 64 bit OSs had double the code in it, double the dependencies, and literally double of everything. Developers were all notified about the change more than 3 years ago and 2 OS versions ago. This was not a surprise.
>I would pick Linux instead.
And you have that option. Godspeed.
A software developer sees Apple finally busting up iTunes which was an overloaded monolithic beast. A software developer sees Apple dropping 32-bit to reduce complexity. This is all refactoring which we'd love to do on our own projects.
And, for someone complaining about that, you sure didn't do much more than come here and tell me that I'm wrong for having different priorities without any of the follow-through that I did to, at the very least, explain my thoughts. You haven't even done that.
It's a pretty typical graybeard rant about the halcyon days. Except since we're in 2019, replace System 7 with Snow Leopard.
export BASH_SILENCE_DEPRECATION_WARNING=1
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
The export I provided prevents this nag message from being displayed for Bash users.They fucked up USB device reattach and my dell dock is a hassle in clamshell mode, which is a multi time per day (sleep and plugin unplug) royal pain in the ass.
Tl;dr is no different to any recent upgrade if you live in a terminal to other hosts.
It’s going to be difficult to make anyone happy with this release that has already decided they don’t like it.
It has been a perfectly informed decision from someone who has been using Macs since 1989. I haven't got out of bed on the wrong side the other day and just decided I didn't like Catalina.
1) Apple makes more margins on Mac hardware.
2) Catalina allows you to basically run iPad apps on the Mac. They wouldn't do this if they were trying to push users to iPad.
3) iPadOS and OSX are fundamentally different. There is no way Apple could ever replace the Mac with an iPad.
Maybe but sells a lot more iOS units.
How can users "move" to a different OS that’s not designed for nor compatible with their device?
Except if you want the latest Xcode version.