Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

iOS 27, iPadOS 27, and macOS 27

apple.com

Post reply on HN
Print view View original

871–880 of 884 posts

Re: iOS 27, iPadOS 27, and macOS 27

#871

Post by hedora »

sleight42 wrote: post #789

I do NOT understand the bullishness on Siri. I've been running the dev builds for month. The thing I hear the most often is, "I'm sorry. Something went wrong."

On 26, for me, the baseline is (1) press the siri button on carplay maps (2) speak destination (3) it shows a screen with a map and blue dot showing my destination, and siri says “Sorry, I do not know where you are.”

The version before that, it’d send me to the wrong destination but typing the speech recognizer output verbatim into maps worked.

So, maybe 27 siri is better? (How could it be worse?!?)

Re: iOS 27, iPadOS 27, and macOS 27

#872

Post by abustamam »

NetMageSCW wrote: post #864
abustamam wrote: post #861

Earlier quoted context omitted.

I thought i was going to greener pastures when I switched from Windows to Ubuntu but Ubuntu native search is pretty bad too. I typed "printer" so I can get to my printer settings and the first three are printer icons/emoji. I cant imagine why these would be more important

The good part is you have the source so you can just fork it, fix the code to prioritize results properly, compile and install it to fix Ubuntu, then see if you can get your patch upstreamed. /s

Just vibe code it my man! /s

Re: iOS 27, iPadOS 27, and macOS 27

#873

Post by bigyabai »

serbuvlad wrote: post #859
bigyabai wrote: post #843

Earlier quoted context omitted.

I am talking about PC gaming, and more specifically modern DXVK/Wine support. There's no need for ports, as the Steam Deck showed. Apple Silicon GPUs are all capable of supporting Vulkan 1.3 and translating DirectX code. Proton 11 supports ARM/FEX natively, which would make Apple Silicon a first-class citizen if you use Asahi drivers. macOS users will be stuck with Game Porting Toolkit and it's lackluster support; iP…

This is entirely a misleading point. DXVK, Wine and Proton are full of patches that exist to support individual games. It is not just a translation layer, as much as a great effort of the open source community to force-port every game in existence to Linux. The effort also includes stuff like ntsync that gives the Linux kernel Windows-y APIs for performance. I doubt Apple has any interest in any of that. I don't real…

That is the point. Valve is maintaining the patches; Apple has to do nothing besides support compliant Vulkan 1.2+ drivers (which their community already does).

Apple doesn't need to implement ntsync to support Proton or DXVK, either. macOS' synchronization primitives do the job just as well as esync or fsync does.

> why are we all going through so much effort to save game devs from writing good OS-independent arch-independent code?

Because Apple doesn't support OS-independent APIs. They also don't support old runtimes, so users will inevitably have to run the Windows version once the native code breaks.

Valve ported several of their games natively to macOS, and almost every single one of them is broken on modern Macs. Valve didn't change the game tech, it's all runtime breakage.

Re: iOS 27, iPadOS 27, and macOS 27

#874

Post by kccqzy »

Someone1234 wrote: post #17

I've been using it for several months since the developer beta came out; overall I'm extremely positive on it. One of their better releases that seemingly focused more on quality and refinements than new-features. Siri is definitely worth using now, even if it remains still a work-in-progress/needs continued refinement. It can surprise you in good ways, but it isn't consistently good yet. The keyboard remains unfixed…

Sure I feel that the Apple bundled apps are better, the design is better, but frankly Golden Gate broke more third-party apps than Tahoe did, including some third-party apps where I had an old perpetual license and had not updated for many years.

Re: iOS 27, iPadOS 27, and macOS 27

#875

Post by prawn »

RileyJames wrote: post #540
nomel wrote: post #368

Earlier quoted context omitted.

It's worse than this! You Type C-H-E then you go to press enter, and it changes the results as you're pressing it, opening the wrong thing! I've turned off all the search targets, except for applications and folders.

Absolutely. The mac spotlight search / bar was one of my favourite features, maybe 10 years ago? But now it’s useless. It also has some strange behaviour when it’s not in focus, but hasn’t been closed. I just leave every application open and command tab to them now.

I found people suggesting Raycast to replace Spotlight search and that's been far better and more consistent for me since I switched.

Re: iOS 27, iPadOS 27, and macOS 27

#876

Post by serbuvlad »

bigyabai wrote: post #873
serbuvlad wrote: post #859

Earlier quoted context omitted.

This is entirely a misleading point. DXVK, Wine and Proton are full of patches that exist to support individual games. It is not just a translation layer, as much as a great effort of the open source community to force-port every game in existence to Linux. The effort also includes stuff like ntsync that gives the Linux kernel Windows-y APIs for performance. I doubt Apple has any interest in any of that. I don't real…

That is the point. Valve is maintaining the patches; Apple has to do nothing besides support compliant Vulkan 1.2+ drivers (which their community already does). Apple doesn't need to implement ntsync to support Proton or DXVK, either. macOS' synchronization primitives do the job just as well as esync or fsync does. > why are we all going through so much effort to save game devs from writing good OS-independent arch-i…

From what I understand you're saying that Apple should provide 2 things: (1) Vulkan drivers and (2) backwards compatibility forever.

I don't really know enough about graphics to discuss point (1). From what I understand, Apple GPUs don't really fit the Vulkan model too cleanly, and the Asahi Vulkan drivers are significantly less performant than Metal (how much of that is due to beta/community status vs. architectural bottleneck I have no idea).

But let's say they provide (1).

Providing (2) would simply be a big mistake. It is a huge mistake of Windows, of the C++ programming language and of the x86 ISA (none of which are very good). Linux distros do not provide this either, beyond the core kernel syscalls and glibc. It is certainly a very big ask and not something trivial.

Re: iOS 27, iPadOS 27, and macOS 27

#877

Post by jotato »

swishman wrote: post #863
jotato wrote: post #579

Earlier quoted context omitted.

Oh my! That solved it! Thank you so much!

Why didn’t you ask an llm if it was bothering you? It would have solved this easily as well

/shrug

This is my first iphone since the original. I thought that is just how it was.

Re: iOS 27, iPadOS 27, and macOS 27

#878

Post by bigyabai »

serbuvlad wrote: post #876
bigyabai wrote: post #873

Earlier quoted context omitted.

That is the point. Valve is maintaining the patches; Apple has to do nothing besides support compliant Vulkan 1.2+ drivers (which their community already does). Apple doesn't need to implement ntsync to support Proton or DXVK, either. macOS' synchronization primitives do the job just as well as esync or fsync does. > why are we all going through so much effort to save game devs from writing good OS-independent arch-i…

From what I understand you're saying that Apple should provide 2 things: (1) Vulkan drivers and (2) backwards compatibility forever. I don't really know enough about graphics to discuss point (1). From what I understand, Apple GPUs don't really fit the Vulkan model too cleanly, and the Asahi Vulkan drivers are significantly less performant than Metal (how much of that is due to beta/community status vs. architectural…

I'm only asking for (1); Apple can keep breaking APIs forever as long as they support the libraries that enable Proton.

(2) is precisely the reason why nobody can port games to macOS anymore, and largely why ARM is a second-class citizen in PC gaming too. You cannot depreciate things like AVX or 32-bit library execution modes, and then demand native builds get made to 20-year-old games. Apple Silicon's ISA extensions like AMX are not a replacement for x86's SIMD extensions, it's not standardized through Arm or supported in Asahi either. Native Mac games need to incorporate Apple's proprietary and unstable tech like Metal and the Apple Silicon microarchitecture, which makes their games unstable and difficult to support in the long term. Translation is Apple Silicon's only choice for game preservation and mainstream game support.

> Apple GPUs don't really fit the Vulkan model too cleanly

This is a misconception that stems from Metal's preference for tile-based deferred rendering pipelines. Vulkan 1.3 is fully viable on the M1 onward, which is enough to support DirectX 12 translation in Proton. The performance of Asahi's drivers are not any worse than the official Vulkan drivers that Arm provides for TBDR-optimized GPUs like the Mali line.

Re: iOS 27, iPadOS 27, and macOS 27

#879

Post by [deleted] »

fodkodrasz wrote: post #597
etatester wrote: post #180

Earlier quoted context omitted.

"Better" is subjective. I've been using iOS 27 beta and other than a few bugs it hasn't been that bad. I only had some minor downgrades in Safari UI, but those are minor and personal. One thing I hated was a downgrade in Photos app on iOS 26 though, that hasn't improved in 27. Unfortunately it seems I was the only one loving Photos on iOS 18. I did jump from macOS 18 to macOS 27 beta though and Safari's UI is abhorre…

Did you see 26? Is it even worse than on 26? It is so bad it got me off from binge browsing... so Nice work Apple I guess.

[deleted]

Re: iOS 27, iPadOS 27, and macOS 27

#880

Post by garbagewoman »

Melatonic wrote: post #867
Agingcoder wrote: post #854

Earlier quoted context omitted.

Fair question. I expect the following from such a system : I set a time limit per app/set of apps,and the phone locks said apps once the limit is reached. In theory, this is what it does, in practice it almost never works : it doesn’t lock, gets broken whenever you upgrade the os, gets broken whenever your child upgrades the os, can be trivially bypassed by a kid, cannot be unlocked when you want it to unlock remotel…

So I don't have kids but in the keynote I remember them making a big deal about totally revamping it in 27. I know they definitely added a way to officially lock it (with a passcode) so your kids won't be able to theoretically just deactivate screen time. I think before you technically could do sorta the same thing (you can restrict almost any app to require FaceID or passcode to unlock). There's also the assistive a…

Wow those supposed improvements sound great. Though what good are features if they don’t work reliably?
Post reply on HN