I think it would be great if Apple provides a secure framework for VMs on iPadOS. Then it wouldn’t be a replacement of iPadOS, but rather an enhancement.
It was updated in March of this year.
And? Of course we want background processes to be sparing, otherwise our battery life would likely suffer. It makes common sense for Apple to recommend developers use background execution modes sparingly, this is just good practice for code development. You don’t want to use any more background execution modes than you need to get things done even on the Mac. This doesn’t mean “iPadOS doesn’t allow background tasks” as Federico claims. Background tasks are absolutely supported in iPadOS, developers just use frameworks for these background tasks to make them more efficient and prevent users from burning through their battery runtime. It also helps in maintaining greater system security if I understand what I’ve read correctly. But having frameworks for such tasks proves such tasks are indeed possible in iPadOS, and also proves that Federico’s claims were wildly exaggerated, just like several others he made in that article.
In a limited fashion, yes it supports multitasking but nowhere close to what macOS can do. Apple actively discourages overusing it for a reason.
So then I think you and I can agree that Federico’s claims that this is impossible on iPadOS are wildly exaggerated and unsubstantiated. And I agree, Apple discourages overusing background execution for a very good reason: efficiency and battery runtime. I’m sure they’d also discourage overuse of background execution on macOS as well. It’s generally good coding practice to not overuse frameworks where it isn’t needed, resulting in lower battery runtime and efficiency for the end user, regardless of the platform you’re developing on.
Sure, I’m not opposed to a setting you could toggle. I just don’t think it’s that big of a deal, since third party keyboards can be used, and a quick swipe up on a key gets you the number or symbol you want. 👍🏻I have and mostly use a Magic Keyboard. Even with a substitution, there are times when the OS forces the use of the standard KB.
IMO it would be nice if Apple gave us the option via a switch in settings - number row or no number row (plus , & .)
I think it’s so that the keys can be more full-sized for touch typists, while still minimizing the amount of screen real-estate blocked by the keyboard. Also I think that it’s likely not a high priority to spend precious development resources on considering there’s already a fix for those who want something different (third party keyboards) and that it may not be a change most people are asking for. 👍🏻
Background processes are 100% limited in iPadOS in relation to macOS: it’s hardcoded in the OS. The way iPadOS and iOS manage background processes inherently limits them. It is not just in a Developer’s control. iPadOS and iOS more aggressively shuts down background processes compared to macOS and virtual memory wasn’t even really in existence in iPadOS until more recently. But virtual memory in iPadOS is still limited compared to macOS and doesn’t do much relatively outside of managing Stage Manager.
What’s the point of this?
This commenter has a history of this kind of behavior. It’s probably best to just ignore him.
The point is that the other poster arguing that it isn't so much limited by the OS. Pretty black and white. However, they are wrong. It is limited by the OS.
But there are cases where devs need to optimize background processes, that’s the case of FCP on the iPad Pro.
Exactly. With iPadOS, there are several frameworks for handling many different kinds of background processes. It’s just that some apps don’t make use of them. This is a completely different situation than the one Federico claimed, where iPadOS supposedly doesn’t allow any background processes…
I agree with you that there are things in a Dev’s control but because LumaFusion can do certain tasks in the background doesn’t mean background processes aren’t limited by the OS. My point earlier is that background processes are very limited in iPadOS by design and it’s not accurate to state or imply it’s mostly under a Dev’s control. I’m not saying you said that.
Not hollow at all. Very limited background processes. And iPadOS does not have the virtual memory capabilities of macOS. It swaps memory frequently. It can’t sustain the type of unlimited multi-tasking that macOS allows. It’s hard-coded into iPadOS.
I think you are under the impression that we are comparing iPadOS to macOS, when that’s far from the case. We are only highlighting the misconception that iPadOS does not allow background processes, that’s it.
Yes. Because despite supporting overlapping use cases, the design intent for the iPad is not the same as a Mac. The iPad is a tablet that is optimized from silicon to software for lean-back / contemplative tasks where singular focus is beneficial. The Mac is optimized for lean-forward / production tasks where multitasking is beneficial. This does not mean that either cannot be used for the other‘s optimized use cases, it just means that one will perform its optimized use cases better than the other.
Exactly, we’re simply pointing out that Federico and other’s claims that iPadOS doesn’t allow background processes is completely false, as background processes are in fact support in iPadOS, they are simply managed with frameworks to keep them efficient and prevent abuse of the system.
If that's it, then yes, iPadOS does allow background processes. I've been in software development for 12 years, and have teams that have developed for macOS and iOS/iPadOS. The multi-tasking in iOS/iPadOS pales in comparison to macOS, but there are background processes that are possible in iOS/iPadOS. If someone is saying flat out that iOS/iPadOS doesn't allow background processes, I wouldn't agree with them either.
