> On macOS memory can be paged to/from disk. On iOS it isn’t and applications must free memory when asked or be terminated
Not sure what you meant by that, you always could `mmap` files into memory on iOS. Back in the 32 bits days there was a ~700 MB limit due to the address space, but there aren't anymore nowadays with 64 bits. If `didReceiveMemoryWarning` is called on your app, then you need to free resident memory but the kernel will take care of dumping file-backed memory pages for you.
> Back in the 32 bits days there was a ~700 MB limit due to the address space, but there aren't anymore nowadays with 64 bits.
Not true, unless something changed recently (definitely more recently than the 32->64 transition). All iPhones have a virtual memory limit (although the limit is higher on phones with more physical RAM).
I know this for sure because several years ago I was the main person in charge of reducing OOM kills on the Facebook iPhone app and virtual memory exhaustion on 64-bit phones was definitely an issue.
That's memory mapping. This is memory paging [1]. I.e. Windows pagefile.sys, Linux swap, macOS swap files. iOS does not have swap files, only memory compression. If you're on a Mac, open up Activity Monitor, go to Memory, and at the bottom there is `Swap Used`. That doesn't exist on iOS. So, if more memory is used than available, applications will need to free memory or be terminated. Unlike macOS, where some used memory will be swapped to disk to allow other stuff to be loaded into memory.
It's most likely just disabled rather than being completely different/non-existent. But yes, the application model is built around limited to no multitasking.
It's not the same version of OS X that ran on Apple's computers. The "it's OS X" was more for marketing, they just share the same "core".
You could argue that the iPhone currently still runs macOS if you used the same definition today. They share kernels (iirc Apple always kept the ARM patches to Darwin closed-source), BSD-based userlands and the iPhone used versions of the macs application libraries.
A big difference is the iOS and macOS use different compositors.
> An investigation based on the largest leak of documents in British political history. The Labour Files examines thousands of internal documents, emails and social media messages to reveal how senior officials in one of the two parties of government in the UK ran a coup by stealth against the elected leader of the party.
Politician smeared during election? Shock horror, it happens during every election.
Leader of the party can't unite their own party so there is a plan to oust them? That's politics.
Jeremy couldn't particularly unite the party, didn't take the center ground, and while I don't think he was a true antisemite there were enough mis-steps there that it meant that the claim could stick (along with the IRA sympathizer claims).
So, the chains broke when doing an emergency braking and the load crushed the pick-up? I clearly see that the driver was at fault, but aren't loads also not supposed to easily escape their tie-downs?
Some loads like this one are so heavy that you just can't defeat their inertia, hence why you go slowly and have a large escort. It couldn't be stopped that quickly just due to the nature of the load.
At some point if you're getting behind the wheel of a vehicle on the road, you have some responsibility yourself. If you're not looking where you're going at all and drive into the path of a heavily-escorted million-plus-pound load and it ends up crushing you because of the sheer physics of the situation, that's on you. There's a hundred other more likely ways to kill yourself on the road if you're not looking where you're going, that don't involve such unusual cargo.
And also, from looking at the photos of the scene, it looks like the driver may have turned quickly to attempt to avoid the crash, and the load continued on of its own inertia and overturned the entire rig, which is an issue caused by top-heavy torque that doesn't care how tightly the load is tied down at all.
Most computers can count to 2^32-1, and many can count even higher! They can also string words together grammatically, which means they are one step away from an artificial general superintelligence explosion.
But when non-human animals use AAC systems, or vocalise words directly, to express wants or needs, they aren't really talking, because they don't use tree-like grammars.
Isn't because in Cars the character itself is the IP, not the actor? For example, if Owen Wilson started cosplaying as the Cars character and making money out of it, he could be sued.
> I don’t know if signatures are verified before or after running but the binary probably won’t even run without being signed by a paying Apple Developer anyways.
It's before. You can code sign and verify macOS binaries with any certificate you wish, including a self-signed one (useful in case you want your private iTerm fork). Note the plugin should be signed with the same certificate as the iTerm app [1], just using a paid account won't work.
Opioid addition is a major cause, yet Fentanyl is popular because the margins are INSANE while access to prescription opioids became much more restricted.
In 2019, Indian companies were a major source of precursors as well [0], yet Indian authorities cracked down on this path [1]. Meanwhile, Chinese authorities turned a blind eye [0].
That said, China is semi-federal as well, and depending on which Province the companies are from, it might be difficult to crack down, especially given that Chinese organized crime has transnationalized in Myanmar and Cambodia [2]
None of this can actually work at scale without financing and ease of operation, and the fact that authorities in multiple countries are turning a blind eye and sometimes actively using Organized Crime as a hybrid tool of power projection (eg. Triads in the Chinese diaspora, Punjabi Organized Crime in the Indo-Canadian Diaspora, the Russian and Caucuasian Vorys, etc)
That's how you have a DoJ lead brothel crackdown in DC and Boston that was because they were being used as an attempted honeypot [3]
Not sure what you meant by that, you always could `mmap` files into memory on iOS. Back in the 32 bits days there was a ~700 MB limit due to the address space, but there aren't anymore nowadays with 64 bits. If `didReceiveMemoryWarning` is called on your app, then you need to free resident memory but the kernel will take care of dumping file-backed memory pages for you.