LeoNatan25

You can still turn it off. In Content Restrictions there is a drop down to limit to the old Siri. There is also a prompt, if you try to turn off Siri completely, to revert to the old Siri. Then that setting applies to the Watch too.

Well, Prism is likely to be with us for a decade, if not more, since Microsoft actually cares about backwards compatibility, whereas Apple much less so, and I guess, to them, we're at a "good enough" state. So Microsoft releasing it is less likely, but Apple could, especially after it is done. But I suspect some asshole sees a "competitive advantage" somewhere, and won't sign off a source release. What a gut punch for the team that worked on it.

Looking forward to a future look at Rosetta 2. Thanks!

Any equivalent look at Apple's Rosetta 2? Perhaps if author has time and availability of hardware, they can have a similar look. Rosetta 2 is going away next year, and it's a shame, even if from a purely technical reason. Apple will never open source it.

Al Jazeera. Nope, not clicking on that qatari propaganda garbage.

Grifters to the grift god

+9001 agree, this arms race is doomed.

Good pun. Not a typo for me.

Because they also want to tell new stories. It’s never just about the graphics, unlike most modern video game “remasters”, for example.

This is a really good video. The entire series of videos is great. Thanks for posting!

So exactly the same result as video games using Unreal Angina 5. Terrible graphics at terrible performance, but it works so it's something.

Haha, "ton of optimizations" is quite the overstatement, given how terrible games run even on the highest end PC configurations, let alone consoles.

Original Reddit thread: https://www.reddit.com/r/buildapc/comments/1qhby2u/did_i_get...

Given enough motivation, access control is irrelevant too. See early Windows "private" API that was used for decades and Microsoft supported despite being "private", because they knew it was being used and they (used to) care about their users.

What a stupid and ridiculous thing to do in 2024. The budget overhead of storage, serving, traffic, bulletin-board software maintenance and moderation is negligible for a company like Autodesk.

This is likely the idea of some idiot middle-management clown that had to show "progress" and "impact" to their own management in order to get a performance bonus.

Spoken like a real iOS zealot. Some of us remember when macOS or OS X or Mac OS X was just a unix, and are indeed uncomfortable with where Apple took macOS in the past decade or so.

For us, there are still options on the Mac: https://gist.github.com/LeoNatan/b1cf77e1a0df2558f02631656e5...

Yes, but you can often still figure out what the name is if you pause in that method and print _cmd ($arg2), or look at the calling stack entry and see what selector string was used.

> Requires Ace Pass data plan $9.99/mo.

LOL

To all the downvoters, this is sarcasm.

This “article” reads a lot to me like a CharGPT generated drivel. Material for maybe two paragraphs at most, spread over a book of nonsense.

So far, you are the only one making a fool of themselves.

This is probably a snarky reply, but here is the serious answer: proportional fonts, with appropriate kerning, is a lot more legible than monospaced font. There is a reason why the press moved into that direction once it was technically feasible. But the same people that bring books as an example why 80 character line length should be enforced would gag at the notion of using proportional fonts for development. It just goes to show that none of these things actually matter, it’s just legacy patterns that remain in-place from sheer inertia, with really very little relevancy today other than the inertia of the past.

> 80-characters-per-line is a de-facto standard for viewing code. Readers of your code who rely on that standard, and have their terminal or editor sized to 80 characters wide, can fit more on the screen by placing windows side-by-side.

This is one of the silliest practices to still be enforced or even considered in 2024. “Readers” should get a modern IDE/text editor and/or modern hardware.

Imagine if China users could just visit a website and install apps.

Full Carbon was there until the 64bit transition officially, but much of it remained and still remains until now. For example, Apple only started using AppKit to draw menus in Sonoma; it was Carbon until now.

This isn’t an example of that. Have you looked at the code? This uses ObjC and Cocoa implementations in an unintuitive method. Nice exercise to learn about the ObjC runtime, but has zero practicality or use.

This uses the ObjC runtime to obtain the underlying ObjC method implementation functions, to call directly, instead of relying on the runtime to call them. If you find this more elegant than a wrapper with some ObjC, good for you.

The linked project also uses Cocoa, and guess what, considering Cocoa itself is written in ObjC, the linked project also uses OBjC “unknowingly”.

Considering CodaFi works for Apple now, he knows. Spoiler: he knew 11 years ago too.

Wait until you hear where much of the technology in your iPhone, Mac, Windows, Intel and so much else comes from.

With idiots like these, no wonder tech companies in the US look to hire in Israel.

Your posts here seem of the “just asking questions” variety—no substance other than being counterculture. Do you have any proof or resemblance of any logical reason to think this?

> 10+ bits. Jpegli can be encoded with 10+ bits per component. Traditional JPEG coding solutions offer only 8 bit per component dynamics causing visible banding artifacts in slow gradients. Jpegli's 10+ bits coding happens in the original 8-bit formalism and the resulting images are fully interoperable with 8-bit viewers. 10+ bit dynamics are available as an API extension and application code changes are needed to benefit from it.

So, instead of supporting JPEG XL, this is the nonsense they come up with? Lock-in over a JPEG overlay?