Finally! They fixed my Image Capture bug! Now I can import pictures from my iPhone AND they will be deleted from the iPhone. I've only imported 7 movies at one time with no problem. So far, so good...
macOS Catalina 10.15.5
361–370 of 387 posts
Re: macOS Catalina 10.15.5
#362Earlier quoted context omitted.
I was just about to let the 2020-003 Security Update run on Mojave, but after this warning I will leave that well alone. Apple had a great OS once, but now they are losing me more with each update. Can't buy new Mac HW either any more, since it will be systematically unable to run the 32-bit SW I need. Apple forcing decades-long users off their platform to Windoze and Linux is just bizarre.
Not installing security updates with large numbers of pretty critical fixes[1] doesn't sound too smart to me. 1. https://support.apple.com/en-us/HT211170
Putting in a user hostile feature in a security update, leading to people to not update, doesn't sound too smart to me.
Re: macOS Catalina 10.15.5
#363Earlier quoted context omitted.
Not installing security updates with large numbers of pretty critical fixes[1] doesn't sound too smart to me. 1. https://support.apple.com/en-us/HT211170
Putting in a user hostile feature in a security update, leading to people to not update, doesn't sound too smart to me.
[deleted]
Re: macOS Catalina 10.15.5
#364Earlier quoted context omitted.
Not installing security updates with large numbers of pretty critical fixes[1] doesn't sound too smart to me. 1. https://support.apple.com/en-us/HT211170
Putting in a user hostile feature in a security update, leading to people to not update, doesn't sound too smart to me.
Why? Catalina has lots of security improvements so it's a net positive for security if more people upgrade.
Re: macOS Catalina 10.15.5
#365Earlier quoted context omitted.
Putting in a user hostile feature in a security update, leading to people to not update, doesn't sound too smart to me.
Why? Catalina has lots of security improvements so it's a net positive for security if more people upgrade.
But it's a net minus for usability that it can't run 32-bit software any more. That makes it a no-go for some of us, and Apple knows that, so all the nagging to “upgrade” is pointless anyway.
Re: macOS Catalina 10.15.5
#366Earlier quoted context omitted.
Why? Catalina has lots of security improvements so it's a net positive for security if more people upgrade.
But it's a net minus for usability that it can't run 32-bit software any more. That makes it a no-go for some of us, and Apple knows that, so all the nagging to “upgrade” is pointless anyway.
So because 0.5% of people have some dodgy 32-bit software that they cannot or have not updated, Apple should just not bother trying to make the rest 99.5% of people update?
Doesn't seem smart.
Re: macOS Catalina 10.15.5
#367> Battery health management is on by default when you buy a new Mac notebook with macOS 10.15.5, or after you upgrade to macOS 10.15.5 on a Mac notebook with Thunderbolt 3 ports.
Unfortunately... this update does not help everyone. I have a MacBook Pro (Retina, 15-inch, Late 2013) and these changes in the System Preferences are not visible. This quote was found only when digging further in the "How to control the battery health management feature" instructions.
Re: macOS Catalina 10.15.5
#368Catalina decided to remap my paragraph key to "ö" this week (using a 3rd party Swedish Dvorak layout). Remaking the layout to the proper symbol works for about an hour. It is my Emacs prefix for functions I don't consider important enough to warrant their own direct key bindings. Annoying doesn't cut it. I haven't done a factory reset yet, but I started backups today to be able to. Catalina is a disaster. I got my Ma…
So: The error seems to be that the keyboard assistant expects qwerty. It must have run some time, and it wanted me to press the button next to the left shift key, which on svdvorak is "ö". I had to delete the library/preferences/com.keyboardsomethingsomething and redo the keyboard identification and press the "Now it works.
Re: macOS Catalina 10.15.5
#369Earlier quoted context omitted.
> binary diffs aren't worth the complexities they introduce anymore Noob question: Why are binary diffs impractical? Is it because the (compiled) object code layout dances around too much? If true, isn't that fixable? Meaning: make the order more stable, to minimize the size of the diffs? I recall a recent story/post about boosting runtime performance by optimizing object code layout. Sorry, I can't refind that artic…
Yep, and they use Courgette for all of their Chrome/Chromium updates. It's why no one ever sees long "Downloading update..." progress bars in that browser anymore. 100KB binary diffs are typical. Blink (no pun intended) and you'd miss the download.
Result! Thank you.
Skimmed the landing page, original paper. Courgette infers program's structure for smarter diffing. My half-baked notion is somewhere in between.
Re: macOS Catalina 10.15.5
#370Earlier quoted context omitted.
But it's a net minus for usability that it can't run 32-bit software any more. That makes it a no-go for some of us, and Apple knows that, so all the nagging to “upgrade” is pointless anyway.
So because 0.5% of people have some dodgy 32-bit software that they cannot or have not updated, Apple should just not bother trying to make the rest 99.5% of people update? Doesn't seem smart.
I didn't say that. But taking away the option to explicitly tell the OS to stop nagging me is still a user-hostile move.
So, you are saying that all 32-bit software is by definition “dodgy”? But let's break it off here since I realize that disagreeing with you may not seem smart.