Latest update to the MarsEdit blogging tool includes this fix:

Work around a crash that could occur when waking from sleep on a Touch Bar-enabled Mac.

Sounds like the shiny new solution-in-search-of-a-problem hardware wasn’t thoroughly tested before shipping.

It seems like just days ago that Adobe had to fix yet another critical security hole caused by their years of tarting up Acrobat (you remember, the “document reader”) with all sorts of unrelated, and generally unwanted, interactive features. Oh, wait, that was last month; it’s Flash that had critical security holes fixed two weeks ago.

Good thing you’re a security-focused company who would never do something stupid like introduce brand-new malware vectors into all of your products. Oh, wait, you’re automatically, silently processing calendar invites and photo-sharing email, no matter who they come from, encouraging spammers to inject data into your system. This not only creates annoying pop-up notifications, but adds new ways to get people to click on malware-infested URLs.

Then again, you still ship every Mac with a browser that will auto-open “safe” file formats when you download them (including… wait for it… PDF files), so maybe the real story is that you were never security-focused to begin with.

[Update: just got one of these, on my almost-never-used icloud account (so, truly random spamming attempt), and had to follow the 6-step process on icloud.com to get rid of this terrible default setting. Nitwits.]

Why does attaching the Thunderbolt-to-Firewire adapter reset the USB3 bus on my MacBook Pro, unmounting the external drives?

Pick two. Or, if you’re feeling less charitable toward Apple, one.

"Just today: My iPhone 6 rebooted after I changed the home screen wallpaper. Tapped a new image in the wallpaper settings, and poof, it rebooted. Worse, it never stopped rebooting. Endless reboot cycle. Now I’m doing a full restore with iTunes. After changing my wallpaper to a different image."

(of course, anyone who buys brand-new Apple designs on launch day is playing with fire in a fireworks factory…)

(not that anyone else’s first shipment of new stuff is necessarily glitch-free, but Apple does seem to be particularly bad at it sometimes)

Update: I followed the link from the article I linked, and while reading it… Safari crashed.

[Update: iOS7 UI errors tumblr; looks like shooting fish in a barrel.]

Most significant line in the Ars Technica review of iOS7:

Nothing is ever illegible, but you may run into mild readability issues that didn’t exist in iOS 6.

The screenshots show that they really don’t care about people with less-than-perfect vision. The spidery little Helvetica Neue text looks gray even when it’s white, and actually setting it in gray is even worse. The fact that they had to add a semi-hidden “bold text” option really reinforces the impression that they’re slaves to a design methodology that didn’t stand up to user testing.

And be sure to check out the “animation durations” video clip on page 3; yes, major interactions with the device will take longer because the designers want you to see what they did to keep the OS from running on older hardware.

Okay, there is a more significant line in the review, if you have an iPhone 5:

Our Verizon iPhone 5 running iOS 7 burns through its battery more than three hours faster than the exact same phone performing the exact same test with the exact same settings under iOS 6.

All devices get worse battery life thanks to Apple’s new design, but only the just-replaced model sucks so horribly that there’s sure to be a major patch coming soon.

…the black cable controls fan speed. I’ll need this information again soon.

The quick side-by-side images here (note that the third image has the new crap on the left instead of the right) suggest that Apple has thrown out everything they might ever have known about accessibility. Tiny! Gray! Low-saturation! Low-contrast! The weather image is particularly hilarious, with the ever-so-thin white font on a light background.

Not that the old one was any great shakes when it came to font size, contrast, and color-deficiency-awareness, but they thought this was good enough to show off to the world, so it’s unlikely they’re going to make drastic changes before release.

Why is it that when I have a block of text selected, and I wish to drag it somewhere, that you insist on having me click on a pixel that’s part of one of the characters in the selection. Not “inside the bounding box”, not “inside the enclosed area”, but actually “on a pixel whose color was set by drawing the character”, so that with black text on a white background, only the black pixels count. And not just for dragging a block of text around, but for dragging a dozen messages to another folder in Mail.app, etc.

I’ve been fighting it for years, but the simple shapes and bold strokes of the latin alphabet are fairly easy targets, so it used to be a minor nuisance. But with kanji, it’s a real pain in the ass. Well over half the time, when I try to sort email with kanji senders and subject lines, attempting the “drag to folder” action will instead result in the “extend selection range” action. Dumb, dumb, dumb.

Ordinarily, I’d expect that the lessons learned working with the crude accuracy of poking an iPhone with a finger would have taught you something about requiring excessive precision in selection, but I’ve actually used an iPhone, so I know you haven’t figured it out there, either.