Juli Clover:
Apple today released a new supplemental update for macOS Catalina, nearly one week after releasing the first supplemental update and two weeks after the launch of macOS Catalina.
Mr. Macintosh:
The patch notes for (19A602) are exactly the same as (19A603)
Howard Oakley:
It’s not yet another emergency update at all, but the result of Apple updating the security certificate on the original 10.15 Supplemental Update (or 10.15 Update as it seems to be called officially).
[…]
Not only that, but if you have already installed the first version of the update, you won’t be offered the second – there’s no point. The only value of the new version is for those Macs which haven’t had the original update applied yet.
If that’s the only difference, why is the new version a full megabyte larger?
Previously:
Mac macOS 10.15 Catalina
Brent Simmons:
We very much want to use SwiftUI, and we believe it’s the future of Mac and iOS development — but emphasis should be on future, because it’s not quite ready in the present.
Which should surprise nobody, given that it’s so new. But I thought it might be interesting to know exactly what issues we ran into when using it.
It’s no secret that the available controls and features are much more complete for watchOS than for iOS or macOS. But this post is an example of some limitations and bugs around areas that you would expect to work.
Overall, SwiftUI seems less suited than Swift itself to incremental adoption because, although you can make a hybrid UI that includes regular Cocoa views, it looks like you can run into a dead end where you have to back out and redo the container/controller as well.
Update (2019-10-23): Jeff Johnson:
“SwiftUI will be great next year” is the new “Catalyst will be great next year”.
Colin Cornaby:
Important distinction: SwiftUI isn’t wrong, it’s just small. There isn’t really a downside to release a small, base API early.
Catalyst is kind of the opposite to this. Release everything, and then try and pick up the pieces afterwards. You get the advantage of having all your API, but the downside of it not working right. That’s harder to pivot from without breaking things.
Jason Brennan:
I was quite surprised to find it doesn’t offer any rich text display or editing. You can style text with fonts and colours and the like, but the style applies to the whole run of text. There’s no equivalent components for creating a rich text editor in SwiftUI yet.
Cocoa Bindings iOS iOS 13 Mac macOS 10.15 Catalina NetNewsWire Programming SwiftUI watchOS
Aimee Green:
Police wanted to search the contents of an iPhone they found in Catrice Pittman’s purse, but she never confirmed whether it was hers and wasn’t offering up a passcode. Her defense attorney argued forcing her to do so would violate her rights against self-incrimination under the Fifth Amendment of the U.S. Constitution and Article 1 Section 12 of the Oregon Constitution.
But a Marion County judge sided with police and prosecutors by ordering Pittman to enter her passcode. On Wednesday, the Oregon Court of Appeals agreed with that ruling -- in a first-of-its-kind opinion for an appeals court in this state.
Via John Gruber:
If you’ve got the password written down on a sticky note and the police get a warrant to search your home and find it, that’s evidence. But being compelled to produce something in your mind is the definition of self-incrimination.
Previously:
iOS iOS 13 iPhone Legal Passwords
Ashley Bischoff:
I ran into the same problem that you did with my ScanSnap no longer working on recent versions of macOS. And I ended up trying exactscan.com since it claimed to work with lots of scanners.
And not only does it work but I might even like it better than ScanSnap Manager!
ExactCODE:
With macOS 10.15 “Catalina” Apple introduced many incompatibilities and we where actually left with the impression that Apple will address some of them as well as some more bugs before releasing Catalina to the public.
After releasing the Catalina Golden Master build to developers on October the 3rd, we immediately finished fixing any new crash and issue we could find over the weekend. In our opinion, leaving developer just four (4!) days over a weekend with a public release on October the 7th is not very professional. While we still updated our applications in time, Apple did not review them for the AppStore, and instead rejected them first for a crash (sigh!), and later for requiring UI changes, including showing a Save As panel for each generated file. Now this may not sound like much, this is a serious issue for a document scan application which easily generates hundreds of files in an hour, and thousands of files a day, with file names automatically generated, either thru counters, or advanced auto-id features, such as barcodes.
It’s ridiculous for shipping a bug fix to be conditioned on making a major user interface change to an app that’s already had 100 updates approved. And, in this case, the proposed “fix” sounds like it makes the app much worse.
With seven years in the AppStore we were actually brainstorming how we could transition this to financially viable future. We would have preferred Apple to eventually support price reduced upgrades, which Apple to date did not. We could only start a completely new application, or transition to in-app purchases and subscriptions, e.g. for OCR, barcode or other features. Neither of which we are particular fans of, and it certainly does not help that Apple over the years was never really supportive, and usually only caused review drama and took 30% of our sales.
Previously:
Update (2019-10-23): See also: Hacker News.
App Store Rejection Business ExactScan Mac Mac App Store macOS 10.15 Catalina
Tyler Hall:
Why didn’t she know there were options further down the share sheet? Because she’s using an iPhone 8, which happens to be just the right height to perfectly crop the share sheet.
With invisible scroll bars, this sort of thing can happen with web pages and Mac apps, as well.
Update (2019-10-25): See also: Hacker News:
Ask Adam:
This is a perfect examination of a huge issue in Apple’s UI design direction. Almost every day I need to reassure novice users that it’s not their fault they don’t know how to work their devices. So many critical features have become completely undiscoverable.
John Gruber (tweet):
In the early era of GUI design, we celebrated affordances. Any view that was scrollable was very clearly scrollable. We, as an industry, got away from that as the basic concepts of using a GUI became part of daily life for everyone. In the post-iOS 7 era, though, Apple seems outright opposed to affordances. […] Just by looking at it, there’s no reason to think there’s more. But “just by looking at it” is the way user interfaces should be designed.
Edward Morbius (Hacker News):
But no, take a tablet, add keyboard, give it a 9-10 inch (~20 cm) screen, and take away every last flipping goddamned means developed over 45 years of graphical user interface design for flipping telling where you are in a document and efficiently going elsewhere.
This. Is. Not. Progress.
Update (2019-11-01): See also: Evolution of the Scrollbar (via Timo Perfitt).
Update (2019-11-06): See also: Hacker News.
Design History iOS iOS 13 iPhone iPhone 8 Messages.app
