Blame cheap-ass management for that, not MS. It was only ever meant for home and student use.

I guess making sure NEW CUSTOMERS CAN’T GET THEIR DATA INTO YOUR HIGH END PRODUCTIVITY SUITE is just good business then?

No, this was typical 1990s “we don’t need to make good decisions because we’re a monopoly” Microsoft.

deleted by creator

A constructor can’t be async so now I need to restructure my code to use async factories instead of constructors

It sounds like you’re trying to do OOD/OOP. In js that’s usually not the way to go. You might want to restructure into a more functional architecture anyway.

Thus insisting on any other way is a major flaw in the developer not the language.

I mean, I understand the idea, but this is a pretty asshole way to frame it. I don’t think I deserve that, and certainly OP doesn’t deserve that.

From browsing your other comments on this thread I understand that you are in a context where you can’t await, that you expect the invocation to take very little time, and that the library offers no complementary sync interface.

As far was I know you’re stuck in this case. I consider the stubborn refusal to add “resolve this promise synchronously right now” a major flaw in js.

It’s standard for operations that take a while and can be performed asynchronously.

What’s your problem with it?

deleted by creator

They are on the file system in /private/var/mobile/Media, and no, they are not accessible using the file app. Apple, what can you do ;)

Yes, that’s the successor document. You can also use the old iPhone 4 era iOS security guide, the file system details are not a fast moving target. The addition of the Secure Enclave changes things a bit.

Anyway, the idea is that data only hits disk encrypted with a per-file key that is stored with the directory information. When you delete a file, the key is obliterated, rendering the deleted data unrecoverable from block storage. The explanation proffered by the journalist that data isn’t really deleted when you delete it from disk, doesn’t hold. Because it is. Or at least the key to it.

A more likely explanation is spare copies either in the cloud or on the device not getting cleaned up. But deleted files on iOS are proper gone.

The iOS security guide, for example?

It’s a fascinating document.

Cool. Do openshift and keycloak next!

Fuck yeah Brexit

This could be more innocent than it sounds. Computer data is never actually “deleted” until it’s overwritten with new 1s and 0s — operating systems simply cut off references to it.

This is emphatically not true on iPhones. If it’s surfacing deleted images, it’s a big deal.

Unless you put the reader in the doorknob, that’s not going to do you any good. The range on those things is a fucking disgrace.

I smell a serious compromise…

This is not the craziest conspiracy theory I’ve read today, but it’s definitely top 3.

Filling an issue quickly is good etiquette. Then you can discuss in the ticket the best way to solve/work around.

FFMPEG is a core technology. You literally cannot do anything with video without touching FFMPEG at multiple places in the stack.

The fact that we have billions of dollars of revenue flowing through that software every day, but we rely on VOLUNTEERS to maintain it shows exactly how hollow the whole SV entrepreneur culture really is.

Bunch of fucking posers wouldn’t know performance code if it kicked them in the face.

It’s also about cable wear and tear. With a molded, fixed cable you can do proper boot and strain relief. A pluggable charge cable would be ribbons in like three months.

Lemmy is full of people that feel they are owed stuff for free. And, I mean, it’s working out for them so far, so I understand why they would consider Apple products waste of money.