Archive for October 30, 2019

Wednesday, October 30, 2019 [Tweets] [Favorites]

Google to Stop Indexing Flash

Google (via Hacker News):

Flash is disabled by default in Chrome (starting in version 76), Microsoft Edge, and FireFox 69. Soon, we’ll also move on from Flash in indexing for Google Search.

Previously:

Twitter for Mac 8.1

Nolan O’Brien:

Along with all the improvements that go into Twitter for iOS, we’ve also worked on some Mac specific things

[…]

Fixed: scrolling would temporarily stop working when closing certain windows using ESC key

Fixed: secondary clicking on a username would break secondary clicking for remainder of app session

Fixed: when under the Messages tab, navigating into “Message requests” would not offer a way to back out other than clicking the Messages tab again

Fixed: some windows could be dragged from anyone in their UI to move their window.

[…]

It’s good to see them iterating quickly. These look like a bunch of Catalyst-specific fixes, mixed in with more general improvements.

Leo Natan:

The new version is a great improvement!

I am seeing a consistent CPU usage when the app is idle.

Previously:

Update (2019-10-31): Nolan O’Brien:

We have submitted Twitter for Mac v8.1.1 for review w/ a change to work around keyboard input issues in secure text fields.

The crux of the change will be to add a modifier to all keyboard shortcuts.

e.g. To “like” a Tweet, the shortcut of L will be updated to be Command-L.

It’s too bad Catalyst requires this. In Tweetbot, I can just press F with my left hand while my right hand is on the mouse.

See also: Mike Beasley (via Hacker News).

Update (2019-11-02): David Chartier:

The fact that dragging a photo out of Twitter to the desktop creates a .webloc file instead of, you know, a photo is…. terrible.

Update (2019-11-05): Matt Birchler:

Text editing specifically is really hard to justify and is not what I would expect from any app on the Mac.

iOS 13.2 Killing Background Apps More

Marco Arment:

I’ve noticed this since the first 13.2 betas, and Overcast users keep reporting it as well: background apps seem to be getting killed MUCH more aggressively than before.

(Especially on the iPhone 11 if you use the camera, presumably because it needs so much RAM for processing.)

Christopher Stephens:

Every single app on my iPhone 7 iOS 13.2 gets killed every time I close. No backgrounding. And each tab on safari when I move to a new one. So frustrating

Cabel Sasser:

This really affected Prompt. Extremely annoying to lose SSH connections when switch apps.

In yesterday’s update we rolled out a semi-cheesy but effective fix: “Connection Keeper” keeps a running GPS-based log of where you connect to servers. Side effect: connections stay alive.

Previously:

Update (2019-10-31): Damien Petrilli:

Well this isn’t good. It means that because of the camera, iPhone 11 are undersized with 4GB of memory.

Scott:

My Note 9 has 12 GB of RAM, 30+ hours battery life, no camera bump and is .03" thicker than an 11 Pro Max. I think apple could have figured it out. The biggest problem with Apple skimping on RAM is the longevity of the device’s usefulness.

Jonas Salling:

I see a lot of speculation that this is about lack of RAM. I doubt it. In our app, we are seeing problem with (some) WKWebView content (ads). App is silently killed after 30s in background. Critical log line attached.

Nick Heer (tweet):

I’m used to the camera purging all open apps from memory on my iPhone X, but iOS 13.2 goes above and beyond in killing background tasks. Earlier today, I was switching between a thread in Messages and a recipe in Safari and each app entirely refreshed every time I foregrounded it. This happens all the time throughout the system in iOS 13: Safari can’t keep even a single tab open in the background, every app boots from scratch, and using iOS feels like it has regressed to the pre-multitasking days.

Joe Rossignol (tweet):

A growing number of iPhone and iPad users have complained about poor RAM management on iOS 13 and iPadOS 13, leading to apps like Safari, YouTube, and Overcast reloading more frequently upon being reopened.

[…]

More complaints are found in this Twitter thread, in this Reddit thread, in the Apple Support Communities, and elsewhere on the web.

Stephen Warwick:

As mentioned Twitter is absolutely awash with reports of poor performance, memory management, and multitasking issues.

[…]

The underlying issue seems to be that Apple may have bitten off more than it can chew. in iOS 12 Apple took the time to relax its frantic feature release model and optimize what it already had in front of it. With iOS 13, it looks like Apple is back to shovelling out as many features as possible, without checking that they all work.

Marco Arment:

Major new bugs introduced in iOS 13.2:

- background downloads often hang forever and never run

- apps get killed in the background so aggressively that iOS effectively doesn’t offer multitasking anymore

…continuing the iOS 13 pattern of breaking long-held basic functionality.

I’m sure Apple has good excuses about why their software quality is so shitty again.

I hear the same thing over and over from people inside: they aren’t given enough time to fix bugs.

Your software quality is broken, Apple. Deeply, systemically broken. Get your shit together.

Marco Arment:

I hear the same stories repeatedly from inside Apple:

- almost no time to fix bugs

- literally zero time to fix older or non-urgent bugs

- far more layers of management since Cook

- problems don’t/can’t get communicated upward

- increased division so teams can’t coordinate

Previously:

Update (2019-11-01): John Gruber:

This bug where apps are getting killed soon after they’re backgrounded is driving me nuts. Start a YouTube video in Safari, switch to another app, go back to Safari — and the video loads from scratch and starts from the beginning.

Matthew Panzarino:

iOS 13 feels like I’m back on iOS 3. Keeps dropping apps out of ram in the background at nearly the pace of 1:1 apps launched-to-quit. Makes drilling down to content or links and then losing them is rage inducing. What a crap ass behavior.

John Siracusa:

On this week’s episode of @atpfm, I compared it to a toddler under a blanket. “You can’t see me! I’m invisible!” But on iOS 13.2, it’s actually true. As soon as you’re not looking at an app, it disappears from RAM.

See this clip, in particular.

Meek Geek:

Turns out this bug has existed since the 1st beta of iOS 13.2, and yet Apple released it (probably due to AirPods Pro’s launch). Marketing-driven releases, again and again. 🙄

It’s so bad I can’t even scroll a web view without it being killed and reloading.

Update (2019-11-02): John Gruber:

If I could downgrade to 13.1.2 I probably would, even though it’d mean losing AirPods Pro support until 13.2.1 comes out -- which perhaps erroneously presumes that this overzealous process reaping is a bug and not a “feature”.

M.G. Siegler:

Yeah, this is driving me insane. Truly bonkers. It’s like Apple is finding new and interesting ways to make iOS 13 worse with each passing update. Can they recall an OS?

Marco Arment:

Why will iOS 14 be any different?

What significant, systemic changes has Apple made?

Do they even think anything is wrong?

Peter N Lewis:

I wonder if the iOS 13 background app massacre issue also affects Find My Friends tracking? I was trying to locate my wife while on the phone with her as she was driving home (to check traffic) and her location remained her start point for the full 20km, no change. Infuriating!

Nick Heer:

I just don’t understand how iOS shipped with this multitasking bug. Surely someone inside Apple with some semblance of power thought “hey, this thing where Safari displays an error and needs to reload every time I switch to it — that’s not good.”

Update (2019-11-05): Dave Murdock:

In addition to the overzealous background app killing issue in iOS 13.2, I’ve experienced & seen on other phones a complete UI freeze for 1+ seconds. IDK what it is, wife is seeing this in Photos, I’m most acutely aware in Safari, all iOS 13 releases have done it, 13.2 worst

Steven Aquino:

I generally don’t gripe about these kinds of things, not in public anyway, but iOS 13.2 is not great performance-wise. It’s even worse on the iPad.

toto:

Wow! #ios 13.2 kills background processes so aggressively that it even kills the webkit process for safari view controllers while you are looking at the page forcing a reaload.

Juli Clover:

Apple today released the first beta of iOS 13.3 to developers, and based on early reports from those who have downloaded the new update, it fixes the frustrating multitasking bug that is impacting many iOS 13.2 users.

Update (2019-11-08): Nick Lockwood:

I’ve seen a few mentions of how aggressive iOS 13.2 is about killing background apps, but this is ridiculous - if I start typing in a web form and let my phone go to sleep even for a second, when I unlock it again it’s killed and reloaded the page, and discarded what I’d typed 🤬

Juli Clover:

According to Apple’s release notes, the [iOS 13.2.2] update fixes an issue that could cause apps running in the background to unexpectedly quit, which led to background apps refreshing more often than normal.